> There's nothing wrong with making a blog post about his early impressions. I totally agree, but he makes a number of conclusions (or at least strong statemen

> There's nothing wrong with making a blog post about his early impressions. I totally agree, but he makes a number of conclusions (or at least strong statements) throughout that, to me, seem premature. For example, in the introduction: "I get the feeling that Go was designed by System Engineers, who focus on implementation." Systems engineers focus on APIs as much, if not more so, than other programmers. Systems engineers build the things at the bottom of the stack, where API design decisions have a fundamental effect on everything built above them. It's definitely worth reading this: http://talks.golang.org/2012/splash.article http://talks.golang.org/2012/splash.article