If people disagree with you, your default assumption should be that they are looking at different evidence than you, not that they are incompetent or stupid.
Maybe Go is fitting into the cultures that succeed, and if that's the case, well it's the better choice, right?
We are. WhatsApp generated a flurry of interest around Erlang. Heroku uses it. I'm sure there are more examples.
Google is at this point already a large corporation and probably already in decline (IMO). The tools they use are optimized for interchangeability of mediocre programmers, not for high productivity from a small team. Go is a perfectly good Java 1.4.
(There's Docker using Go, but I think their whole approach is a bad idea).
We could also look at the open source world. For every riak there are 10 java sucesses of a similar kind.
We'd need to do some real statistics but my bet is that we see no benefit from those languages in terms of success of the business.
But that's not the question, is it? There are a lot of companies succeeding with ruby or node, but also a lot of companies failing with them. I'll bet the strike rate is better for Erlang companies.
(In my limited experience I've seen a 100% success rate for companies that use Haskell and a 0% success rate for companies that use Go, though as you can imagine I don't have a statistically valid sample size)
Go gives you kind of safe concurrency, Haskell gives you actual safe concurrency.
Like these?
https://www.haskell.org/haskellwiki/Haskell_in_industry
https://www.erlang-solutions.com/industries
This line of thinking serves more to call in to question the engineering and management cultures we have than it does to reflect poorly on Haskell and Erlang, and if it's true that Go's essential strength compared to them is that it is well-fitted to these cultures, that's not particularly flattering, however locally practical it may be.