I've recently become a little nervous about the way that people are leaping for Node.js when there are proved libraries in pretty much every other language that are basically Node.js, plus five to ten years refinement and testing, plus numerous other plugin libraries that have been created, refined, and tested too.
If playing with the latest prettyshiny is your goal, have at it and have fun. But for getting real work done on real sites I have a hard time believing it's the best choice.
(If it seems simpler than the existing tech, that's the usual way of things. New tech like this is always simpler. It will eventually be discovered by the Node.js community that the complications present in EventMachine or Twisted or other competition is in fact not there because the developers are stupid, but because they learned the hard way it's necessary complication, for the most part, if you want the stuff to actually work, and in another couple of years, Node.js will end up being just as complicated and for the exact same reasons. If you don't mind not working in JS, you can skip to the end of this process if you pick up one of the other libraries that are already mature.)
I suppose that one of the advantages of NodeJS is that it can learn from the successes/mistakes of the others. Without having 5-10 years of cruft, baggage and backward-compatibility to worry about.
I take your point though. I only know EventMachine a little, and I've never used Twisted. And there's other solutions too. Pick the right tool for the job.
If playing with the latest prettyshiny is your goal, have at it and have fun. But for getting real work done on real sites I have a hard time believing it's the best choice.
(If it seems simpler than the existing tech, that's the usual way of things. New tech like this is always simpler. It will eventually be discovered by the Node.js community that the complications present in EventMachine or Twisted or other competition is in fact not there because the developers are stupid, but because they learned the hard way it's necessary complication, for the most part, if you want the stuff to actually work, and in another couple of years, Node.js will end up being just as complicated and for the exact same reasons. If you don't mind not working in JS, you can skip to the end of this process if you pick up one of the other libraries that are already mature.)