2 ms·

There's nothing wrong with making a blog post about his early impressions. It's just an opinion on the internet. There's millions more out there, and we all pro

There's nothing wrong with making a blog post about his early impressions. It's just an opinion on the internet. There's millions more out there, and we all probably disagree with a few of them. But even aside from that, it's valuable to have someone's early impressions of a language. They may change later. That's cool. But it's also cool to know what they think early on, because it's fairly likely other people will have the same experience. Whether or not his comments represent misconceptions and inaccuracies, they still report his experience. Other people can benefit from knowing others shared the same experience, and if he blogs later when he has more knowledge they can also see how his experience changes over time. I encourage more blogging of this sort.

jinushaun 14y ago
I agree. User experience and interaction design is more than just buttons and animations. It covers all interactions, included programming languages, that's why the post is valid even if it might be inaccurate.
enneff 14y ago
> 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