His basic point seems to be "use the right tool for the right job", which I think we all can agree with. I've been programming stuff in Go for about half a year now and I'd have to agree with the author - building a website in Go doesn't make much sense, for many of the same reasons building a website in c or java (for me the java process is too slow) doesn't make much sense. On the other hand, the concurrency model is excellent and for services, background processing, doing all kinds of intensive serverside lifting - i.e. traditional java application areas - Go, in my opinion, beats out java and is an excellent tool for the job.