OK, for the record, here are a couple of things missing from this, coming from a 30 yr-exp hands-on architect who has seen the entire evolution :
* The comment about arrogant self-absorbed hipsters was spot on. I shortened my resume as a quick test, and had twice the recruiters calling me from Mountain View.
* Weakly-typed (errors caused by lack of typing)
* Late-bound (runtime errors instead of compile-time)
* Exception handling is not typed.
* Lexicon is not completely defined -- just try to change the order of chained event handlers.
* Exceptions in the parser and JITter and VM -- how they're handled is suspect.
* More abstraction layers that nullify the advantage from the event model.
* Memory usage is horrible. It's for business apps only. DOMs have always been memory hogs. That's just another restriction to add to the list.
However, here's why event models process more:
* Less context-switchingt
* Async threading leads to more throughput
Node.js has a good use on phones for development. Phonegap is excellent.
pff commented on Only Idiots Use Java For High Frequency Trading.
Again, somebody that thinks his things are faster because are done in C++.
My processor does not process bytecode, and yours? LOL