[u84six]

From what I've heard, TJ is working with Go because Joyent wasn't putting enough effort into releasing features for node and he also got tired of JavaScript callbacks. I think node will see some love very soon, and I know there are plenty of ways to deal with callback hell. That's just one guy's feeling. I really love working with node. But definitely looking forward some new features.

[tjholowaychuk]

There are lots of reasons! I'd encourage people to try something new (Go, Rust, Scala, whatever), it's easy to ignore Node's shortcomings sometimes. Community was a big one for me, the "unixy" nature of node+npm is no good when the module quality is pretty poor and the names are completely nonsensical, your app just becomes an abstract blob of code that makes no sense. Go's stdlib is pretty rock solid, nothing in Node comes close IMO.

[izolate]

Having just spent more time at work this week creating PR for bugs in npm modules, instead of doing actual work... I'm starting to agree.

But honestly I think that's just par for the course for any substantially popular language. I don't think Go (or any other language) is inherently immune to this.

[tjholowaychuk]

For sure, there are lots of skillful people working on node as well, I just think the Go team has a lot more experience and it shows.