>>16,17There are if callbacks are everywhere because the execution order of those produce the same kind of problems. Blindly relying on a conceptually unsound platform to fix every problem of concurrency is not only naive but dangerous.
About languages that outperform Node, I gave Haskell as an example in my post. Once again, please read something completely before you reply, it's annoying if I have to repeat myself or reply to plain misquoting constantly.
callback style isn't hard to program in if you have half a brain
Web programming in Assembly isn't hard if you have half a brain. It's your job to show why node.js is worthwhile: Why should I use it if it's harder to maintain and slower than other platforms?
Misplaced sense of beauty in code is a funny term. Is beautiful code not desirable? Is beautiful code impossible? If you write node.js, maybe. But the world isn't node.js, and I sure as hell am not going to maintain callback JS if I have superior alternatives.