Node.JS is a decent platform for developing on, if you know the caveats. You have to be very careful with the modules and frameworks you use -- as mentioned in

Node.JS is a decent platform for developing on, if you know the caveats. You have to be very careful with the modules and frameworks you use -- as mentioned in the article, maturity of modules varies. I know people that have had issues with socket.io and skipped it (and node.js) for their production needs. That said, my aha, gotta be careful, moment was when I was setting up a quick test, picked one of the http-digest auth modules, and had a bug -- actually a completely incorrect digest auth implementation (basic auth was fine). This was the second node.js module implementing digest auth that I used that had a bug that relatively simple testing would have found. (The other bug was around the caching/lifecycle of nonces.) I plan on going back and submitting patches for both of these modules, but the lack of basic testing in two cases of a well known (and documented) feature reminded me that the platform is still in transition. (This is just one example of some issues I've run into) Why I say you have to be careful? For the downsides, there are definite upsides. I needed a simple test https server w/ a rest API and serving a static file -- total lines of code, about 25. A great boon to prototyping. Like any new framework, evaluate it in consideration with your needs.