If you're interested in some harsher views of Go I recommend this article, particularly when the author cites Rob Pike.
Myself I've used Go to rewrite a few webservices. Now that I have, I'm considering rewriting again back to node.js or python. Go's just doesn't offer enough safety advantages to warrant its opinionated style constraints - which often violate gestalt principles - or its unwieldy syntax.
To me, Go appears to be created to satisfy a political/marketing goal rather than a technical one, namely to (a) draw programmers from java and (b) allow companies to hire less capable (cheaper) developers, by keeping the language very simple/restricted and forcing certain style choices.
This isn't necessarily bad, it has been proven that teams with diverse level of experience perform best. But I personally feel that Go isn't promoting diversity, it's promoting 'simple' work, as there is no way for 'more experienced' programmers to use the tools they want in Go.
However, based on salaries for the adverts I've seen in my country over the last year, learning Go as a career move does appear to make sense.
I'll go over the post, thanks!
I don't know if initially Go was created for marketing reasons or not, but the simplicity and the forced style can be a plus in the long run. All code looks the same, the difference is what the code does, not how it is written in the page.
You can still name functions and variable counter intuitevely to make it obscure :D
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.