Gopher Reading List: A curated selection of blog posts on Go

[petercooper]

https://github.com/enocom/gopher-reading-list

[O_H_E]

Similar Rust Reading lists

https://github.com/ctjhoa/rust-learning

https://github.com/brson/rust-anthology/blob/master/master-l...

[gameswithgo]

A list of my videos, teaching programming in Go:

https://gameswithgo.org/topics.html

[guessmyname]

Most of the links point to 3rd-party blog posts that could be taken down any time.

I think a better GitHub project would be to cache the content of those articles — in accordance with their respective copyright terms, of course. I was personally disappointed that not many books have been referenced there, nor formal papers. Good list nonetheless, for people who have no idea what to read or where to start.

[TheAceOfHearts → guessmyname]

As I understand it, at least in the US, there are copyright exceptions for archives.

Perhaps you can suggest to the author that they generate archives [0] for each post and provide a backup link.

[0] https://archive.is/

[HankB99 → guessmyname]

While looking for something on "the other go programming language" I ran across this book list: https://github.com/golang/go/wiki/Books Maybe the creator of this repo didn't want it to be yet another book list.

[more-entropy]

May be somebody could recommend same list about Rust?

[O_H_E → more-entropy]

I had to search that couple of days ago

https://github.com/ctjhoa/rust-learning

https://github.com/brson/rust-anthology/blob/master/master-l...

[kuschku]

So, are those posts available via gopher://, or why is this called a gopher reading list?

[agnivade → kuschku]

Go programmers are called gophers. Nothing to do with the gopher protocol.

[kuschku → agnivade]

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.

[PaulRobinson → kuschku]

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 execution and avoid the use of the word 'set' in computer science. Think that's likely to happen?

[kuschku → PaulRobinson]

Sure, that’s why society has no trademark laws and all names are reused all the time, and we have hundreds of companies all called Apple that make products called iPhones?

Society has realized that having unique names is required to find things and avoid confusion.

[mseepgood → kuschku]

Words can mean more than one thing. Are you new to the world?

[HankB99 → kuschku]

What is "the other go programming language"?

[kuschku → HankB99]

See https://en.wikipedia.org/wiki/Go!_(programming_language)

[pmarcelll → kuschku]

Apple also did it with Swift https://en.m.wikipedia.org/wiki/Swift_(parallel_scripting_la...

[LeoPanthera → kuschku]

It's a pun. Go-pher.

[Jaruzel → kuschku]

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.

[shaftoe → Jaruzel]

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%."

[Jaruzel → shaftoe]

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.

[mratzloff → Jaruzel]

They can coexist.

[g4z → mratzloff]

No.. there can only be one!

[staticassertion → Jaruzel]

There's virtually no confusion...