What would make Node more attractive is if it supported copy-on-write multithreading and gave me a way to cheat and use asynchronous I/O (like a wait(myFunctionThatTakesACallbackOrDeferred) function)
https://github.com/athoune/em-scenario
Note: I still think this approach sucks.
V8 provides a really awesome shared-nothing multithreading scheme via web workers. It's just nobody uses them.
"Node does not modify the JavaScript runtime. This is for the ECMA committee and V8 to decide. If they add coroutines (which they won't) then we will include it. If they add generators we will include them."
See Tim's thread, My Humble Coroutine Proposal (https://groups.google.com/forum/#!topic/nodejs/HJOyNMKLgB8). Warning: long.
So, you don't like javascript? Don't use it.
But you won't beat the control over program state offered by javascript -- not until computers understand their programmers well enough to reason about program state. We need better computers, better computer science, and better programmers -- that's all. Then we can replace NodeJS with something better.
Until then, NodeJS is almost certainly the most tasteful solution to the most common problems. I hope its replacement meets so high a standard.
I'm all for using coroutines to solve this problem. That's the approach taken by my Celluloid::IO library:
https://github.com/tarcieri/celluloid-io
Unfortunately Ryan Dahl is adamantly opposed to coroutines so that's not going to happen in Node any time soon.