Earlier quoted context omitted.
https://en.wikipedia.org/wiki/Gopher_(protocol)#Decline "In March 2017 Veronica indexed 133 gopher servers" https://blog.golang.org/8years "Go has been embraced by developers all over the world with approximately one million users worldwide. In the freshly published 2017 Octoverse by GitHub, Go has become the #9 most popular language, surpassing C. Go is the fastest growing language on GitHub in 2017 in the top 10 wi…
And? Gopher (the protocol) is not dead yet. There's an active retro community keeping it alive and developing it. Just because it's no longer mainstream doesn't mean it should be erased from our lexicon. How about I invent something and call it COBOL, is that OK? If we expect our industry to ever grow up, we need to respect its history, and not keep overwriting it.
Gopher Reading List: A curated selection of blog posts on Go
21–26 of 26 posts
Re: Gopher Reading List: A curated selection of blog posts on Go
#22Earlier quoted context omitted.
What is "the other go programming language"?
See https://en.wikipedia.org/wiki/Go!_(programming_language)
Re: Gopher Reading List: A curated selection of blog posts on Go
#23Earlier quoted context omitted.
So, not only did the go programming language overshadow the other go programming language, their gophers are also overshadowing the other gophers? This is a bit annoying.
Go had over 300 meanings in the OED already. Most people in the community will happily refer to it as 'golang' when talking about the language, and in that context, it is obvious what a gopher is. If you think this is annoying, well, there are a lot of things you can be annoyed about: https://english.stackexchange.com/questions/42480/words-with... In this scenario, we should stop using 'run' to describe program execu…
Society has realized that having unique names is required to find things and avoid confusion.
Re: Gopher Reading List: A curated selection of blog posts on Go
#24So, are those posts available via gopher://, or why is this called a gopher reading list?
Easily fixed: - When talking about Go the language: type it as 'GOpher' - When talking about the protocol Gopher: type it as 'Gopher'. If even just the HN community adopted this, there'd be less confusion.
Re: Gopher Reading List: A curated selection of blog posts on Go
#25Earlier quoted context omitted.
https://en.wikipedia.org/wiki/Gopher_(protocol)#Decline "In March 2017 Veronica indexed 133 gopher servers" https://blog.golang.org/8years "Go has been embraced by developers all over the world with approximately one million users worldwide. In the freshly published 2017 Octoverse by GitHub, Go has become the #9 most popular language, surpassing C. Go is the fastest growing language on GitHub in 2017 in the top 10 wi…
And? Gopher (the protocol) is not dead yet. There's an active retro community keeping it alive and developing it. Just because it's no longer mainstream doesn't mean it should be erased from our lexicon. How about I invent something and call it COBOL, is that OK? If we expect our industry to ever grow up, we need to respect its history, and not keep overwriting it.
Re: Gopher Reading List: A curated selection of blog posts on Go
#26Earlier quoted context omitted.
And? Gopher (the protocol) is not dead yet. There's an active retro community keeping it alive and developing it. Just because it's no longer mainstream doesn't mean it should be erased from our lexicon. How about I invent something and call it COBOL, is that OK? If we expect our industry to ever grow up, we need to respect its history, and not keep overwriting it.
They can coexist.