4 ms·

Every day someone publishes their snowflake opinion on why Go is terrible. Every day, hundreds of highly productive engineering teams write millions of lines of

by 013a 9y ago

Every day someone publishes their snowflake opinion on why Go is terrible. Every day, hundreds of highly productive engineering teams write millions of lines of Go, powering web services and developer tools you use on a daily basis. So I'm inclined to side with the engineers actually putting the hours in instead of the talking mouth bloggers. If there comes a day when Google, or Uber, or Twitch, or Cloudflare comes out and says "Go was a mistake and we're starting to replace our old Go code with this new thing", then I'll start listening.

aaronblohowiak 9y ago
This kind of comment makes me not want to visit HN. You can make your point without being so off-putting.
- CodeMage 9y ago
  Not to mention that the point in question boils down to argumentum ad populum fallacy. The same reasoning could have been applied to Java in its heyday.
  - cwyers 9y ago
    In its heyday? Java is still scads more popular than Go.
crdoconnor 9y ago
From python to go and back again, by mozilla: https://docs.google.com/presentation/d/1LO_WI3N-3p2Wp9PDWyv5B6EGFZ8XTOTNJ7Hd40WOUHo/mobilepresent?pli=1#slide=id.g70b0035b2_1_168 https://docs.google.com/presentation/d/1LO_WI3N-3p2Wp9PDWyv5...
- 013a 9y ago
  There's also a good writeup from Asciinema [1] with a similar theme. These are valuable articles from people who have clear domain knowledge in their problem area, which accurately discuss the pros and cons of both approaches. There's a huge difference between "Go doesn't work for us, here's why, here's what works" and "I don't like Go". The latter should be a Facebook post and has no place on HN. [1] http://blog.asciinema.org/post/and-now-for-something-completely-different/ http://blog.asciinema.org/post/and-now-for-something-complet...
drdaeman 9y ago
It's very simple. There is no contradiction and no reason for name-calling. Go is terrible, but it's also one of the good things we have that can get shit done. Another - and quite notorious - example of "worse is better" principle at works.
cwyers 9y ago
There are many more people being productive in Not Go than there are in Go. Taking this argument to the logical conclusion, we should all be using... what, C++ or Java?

by 013a 9y ago

aaronblohowiak 9y ago

This kind of comment makes me not want to visit HN. You can make your point without being so off-putting.

CodeMage 9y ago
Not to mention that the point in question boils down to argumentum ad populum fallacy. The same reasoning could have been applied to Java in its heyday.
- cwyers 9y ago
  In its heyday? Java is still scads more popular than Go.

crdoconnor 9y ago

From python to go and back again, by mozilla: https://docs.google.com/presentation/d/1LO_WI3N-3p2Wp9PDWyv5B6EGFZ8XTOTNJ7Hd40WOUHo/mobilepresent?pli=1#slide=id.g70b0035b2_1_168 https://docs.google.com/presentation/d/1LO_WI3N-3p2Wp9PDWyv5...

013a 9y ago
There's also a good writeup from Asciinema [1] with a similar theme. These are valuable articles from people who have clear domain knowledge in their problem area, which accurately discuss the pros and cons of both approaches. There's a huge difference between "Go doesn't work for us, here's why, here's what works" and "I don't like Go". The latter should be a Facebook post and has no place on HN. [1] http://blog.asciinema.org/post/and-now-for-something-completely-different/ http://blog.asciinema.org/post/and-now-for-something-complet...

drdaeman 9y ago

It's very simple. There is no contradiction and no reason for name-calling. Go is terrible, but it's also one of the good things we have that can get shit done. Another - and quite notorious - example of "worse is better" principle at works.

cwyers 9y ago

There are many more people being productive in Not Go than there are in Go. Taking this argument to the logical conclusion, we should all be using... what, C++ or Java?