>>12If ``b-but I hate callbacks'' is all you extracted out of my post, I recommend you to double-check your reading comprehension. If you think callbacks are in any way acceptable for a high level of concurrency in 2014, I recommend you to double-check your sanity as well while you're at it.
Haskell solved the problem node.js tried to solve in a completely superior way when it put green threads and an event-driven architecture into its runtime. Another frequently quoted benefit of node.js's model is the lack of race conditions because everything is in one thread. This is not only false, but once again easy to mitigate in other languages through clean, proper concurrency primitives, which node.js doesn't put any kind of focus on. After all, there are no race conditions if there's only one thread, right?
The horrible irony to see here is that other languages are not only more pleasant to use than node.js (might as well call it a dialect of JS) but perform better, too, and I didn't even use languages optimized for concurrency as an example. So node.js is not even a good
trade usability for performance kind of platform, it's just ass-backwards.
There's no reason to use it, and even less of a reason to bring it to the desktop. Let Javashit and nineties paradigms die already, for Christ's sake.