Definitely. The callback style is horrible as a concurrency model. Truly awful. Compare callbacks to goroutines and it's insane how awesome goroutines are. But

Definitely. The callback style is horrible as a concurrency model. Truly awful. Compare callbacks to goroutines and it's insane how awesome goroutines are. But, Node made it easier to write purely asynchronous code and using a language people were familiar with, that's why it became so popular. While Go is has an insanely good concurrency model, Node has it's quick iteration going for it and a large number of packages. Now that generators (coroutines) have made it into V8, the concurrency model of Node is changing, for the better. Node is still very much limited in application (thanks to JavaScript and the event loop.). Whereas Go can be used for a lot of different things. But Node specializes in web applications, in web servers. Thus, it's going to be more productive than a general purpose solution.