I think the article makes valid points, but I'll say this for Golang: at least it has a philosophy and sticks to it. It doesn't try to be everything for everyon

I think the article makes valid points, but I'll say this for Golang: at least it has a philosophy and sticks to it. It doesn't try to be everything for everyone (I'm looking at you, Scala). You pick the right tool for the job, whether you're an individual programmer or an organization. Sometimes that tool is going to be Go, and at least it says on the package when and how it should be used.