Right before HTTP took off in the early 1990's, there was Gopher and for a while it, too, was growing exponentially. It was fast and hosted text, source code, graphics, and any number of other types of files, just not all mixed together in one and the same document. For a while it was winning out over HTTP and making grounds against FTP. But that changed eventually and the rest is history. The MinnPost goes a bit into the history of Gopher with the Rise and Fall of the Gopher Protocol.
(Score: 2, Interesting) by Anonymous Coward on Saturday August 13 2016, @09:28AM
You really don't want to try explaining the name "Gopher" to the team of Indian coders when they come to take your job. See, Indians speak English, but the gopher is an animal indigenous to North America. Indians have absolutely no idea what you're talking about, because there are no gophers in India. Which is really funny because as an American I know exactly what an elephant is, even though elephants are indigenous to India. And I'll take that useless knowledge to my pauper's grave!
(Score: 0) by Anonymous Coward on Saturday August 13 2016, @02:11PM
Not sure why this got flagged 'Interesting', as it seems more like a racist flame bait. In the process you seem to confirm an 'Murican stereotype that the rest of the world has about 'Muricans.
I'm from Europe and we don't have gophers (or elephants), but I know from both what they are.
(Score: 0) by Anonymous Coward on Saturday August 13 2016, @03:21PM
You might know what an elephant is. But you don't know what a jird is.
(Score: 0) by Anonymous Coward on Saturday August 13 2016, @03:36PM
If it had been developed at Oregon State, we'd have had the Beaver protocol.
(Score: -1, Troll) by Anonymous Coward on Saturday August 13 2016, @10:19PM
You don't really need know what a gopher is to use Gopher, much like you don't need to know what Soylent is to use this site.
With that said, trying explain even the simpliest of concepts to Indians is often futile.