Why do they call it Gophercon when it's not about Gopher or the Gopher protocol, servers, or clients at all?
It's about Go, right? So shouldn't it be called something like GoLangCon instead, to avoid confusion with Gophercon events that actually are about the Gopher Internet protocol that's been around and going strong since RFC-1436 with the IANA assignment of TCP port 70 ???
Don't get me wrong. I like GoLang, and there's a couple of Gopher servers and clients written in it, but other than that, Go has nothing to do with Gopher.
And then there's this, designed by the Gopher folks themselves:
Developed by Mark McCahill, Paul Lindner and Farhad Anklesaria from a Campus-Wide Information Service, Gopher was named both for the University of Minnosota mascot, and after “go for” meaning fetch.
Why do they call it Gophercon when it's not about Gopher or the Gopher protocol, servers, or clients at all?
It's about Go, right? So shouldn't it be called something like GoLangCon instead, to avoid confusion with Gophercon events that actually are about the Gopher Internet protocol that's been around and going strong since RFC-1436 with the IANA assignment of TCP port 70 ???
Don't get me wrong. I like GoLang, and there's a couple of Gopher servers and clients written in it, but other than that, Go has nothing to do with Gopher.
The mascot itself is a Gopher and it will also explain the historical way back you probably never knew, me too.
blog.golang.org/gopher
And then there's this, designed by the Gopher folks themselves:
Developed by Mark McCahill, Paul Lindner and Farhad Anklesaria from a Campus-Wide Information Service, Gopher was named both for the University of Minnosota mascot, and after “go for” meaning fetch.
gopher://gopherspace.de/0/menu/WIKI/GopherCon/94/Agenda_in_detail_FINAL.txt
thepracticaldev.s3.amazonaws.com/i...
thepracticaldev.s3.amazonaws.com/i...