home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #27 / NN_1992_27.iso / spool / comp / infosyst / gopher / 1195 < prev    next >
Encoding:
Text File  |  1992-11-17  |  1.4 KB  |  29 lines
  1. Newsgroups: comp.infosystems.gopher
  2. Path: sparky!uunet!sun-barr!ames!agate!stanford.edu!leland.Stanford.EDU!leland.Stanford.EDU!aldrich
  3. From: aldrich@leland.Stanford.EDU (Jeff Aldrich)
  4. Subject: Re: More people would use gopher if ...
  5. Message-ID: <1992Nov17.175202.5688@leland.Stanford.EDU>
  6. Sender: news@leland.Stanford.EDU (Mr News)
  7. Organization: Stanford University
  8. References:  <BxMJLI.n0B@news.cso.uiuc.edu> <92321.102821NLAFLAMM@vma.cc.nd.edu>
  9. Date: Tue, 17 Nov 92 17:52:02 GMT
  10. Lines: 17
  11.  
  12. In article <92321.102821NLAFLAMM@vma.cc.nd.edu>, Nick Laflamme <NLAFLAMM@vma.cc.nd.edu> writes:
  13. > For what it's worth, the problem with "gopher" may be simply that it's
  14. > too cute and meaningless.
  15.  
  16. C'mon, folks.  I refuse to believe that I'm the only one reading this group
  17. old and decrepit enough to understand the significance/origin of the name
  18. "gopher" in this general context.  The term began as a play on words, I 
  19. think in the auto racing community, referring to the kids who ran errands
  20. in the pits, which kids got ordered around with suggestions like "hey kid, 
  21. go for some solvent, go fer some coffee, gopher this'n'that..."  Thus the
  22. general-purpose fetcher of whatever is needful came to be known as a
  23. gopher, ok?
  24.  
  25. ................................................
  26.  Jeff Aldrich    <aldrich@sunrise.Stanford.EDU>
  27.  R&D Engineer    Center for Design Research
  28.                  Stanford University
  29.