I would add: 5. Good documentation (and good culture of documentation) Whenever I have to go look up a Go package[0] and figure out how to use it, I am impres

I would add: 5. Good documentation (and good culture of documentation) Whenever I have to go look up a Go package[0] and figure out how to use it, I am impressed with how good most of the documentation is. Yes, you have to be familiar with the golang conventions, but it seems like accurately documenting libraries is just a thing people take seriously in the ecosystem, and in many others it stops at the good intentions. Also I really like how explicit it all is. I usually learn something more than just an API when I dig into a Go package. So, if you like to nerd out on that kind of thing, Go is one of the best places to do it. [0]: I hate that they replaced godoc.org with this, but: https://pkg.go.dev https://pkg.go.dev