That's the weakest reason to choose Go. I think the other comment made it pretty solid that here on HN we have a lot of top-rated comments and topic involving building an app or rewriting an app in Go.
If the reason is neither Python nor Ruby can do concurrency right out of the box like Go does, then sure this could be a good reason because people in Python and Ruby world would argue which set of tools to use.
I mean Python coder and Ruby coder can argue that Go is not the way to go; static compilation, like whattttttt? Strict type... like what?
I am not very convinced and think that slide is pretty biased - well basically doesn't justify why Go was picked and the tone of the slide makes me think Go is the solution to all the disputes we have in other languages. We have plenty of Go vs Python vs Ruby threads.
Er, but those people tend to be for "their" language, and suspicious of others, regardless. Avoiding traditional rivalries may give them some breathing room, but Go is not somehow outside of the tribal fanboy ecosystem.
Indeed, the "OMG GO!1!" tone of many HN stories and comments on the language suggest that it's diving in headfirst...
I don't think so: I'm guessing a lot of Go programmers where Ruby/Python guys before. My main language before Go was Python (every time I needed to do some non-trivial bashy stuff I went for Python) and now unless I need some esotheric library only available in Python (or Lisp) I go straigt for Go. And still like Python, no big deal. Won't bash a language I still like!
By using Go, it avoids a lot of existing biases. I think that's what that slide is referring to.