Re:Gopher Reading List: A curated selection of blog posts on Go
by shaftoe on Sunday March 04, 2018 @11:10AM
(#16515168)
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 with 52% growth over the previous year. In growth, Go swapped places with Javascript, which fell to the second spot with 44%."
Re:Gopher Reading List: A curated selection of blog posts on Go
by Jaruzel on Sunday March 04, 2018 @11:22AM
(#16515229)
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
by mratzloff on Sunday March 04, 2018 @03:06PM
(#16516379)
They can coexist.
Re:Gopher Reading List: A curated selection of blog posts on Go
by g4z on Monday March 05, 2018 @04:32AM
(#16519837)
No.. there can only be one!
Re:Gopher Reading List: A curated selection of blog posts on Go
by staticassertion on Sunday March 04, 2018 @02:13PM
(#16516028)
There's virtually no confusion...
- 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.