[cel1ne]

I hope you don't mean the JVM by "the cumbersome part". It think is unparalleled in performance, garbage-collection, general dev-ops and monitoring capabilities.

You can run many different languages on it, all nicely contained within the virtual machine.

As far as I know Twitter replaced their Ruby/Rails with Code on top of the JVM for these reasons.

Also I don't think it's good to religiously stick to async/"just one thread" and sync/"one thread for everything". The most performant answer depends on the real world scenario and almost always lies somewhere in between.

[boggydepot]

I think he meant the js not java. Question about node js, So async model is the good part, js is the bad part, why use js then?

[my123]

The JVM is nowhere near as flexible as the CLR.

[cel1ne]

The JVM probably lags behind in some aspects. But it's ecosystem is way larger and not biased towards Windows.

[peterashford]

In what way?

[my123]

The CLR can be used to run C++ code compiled with the C++/CLI (/clr:pure) setting of MSVC. Java apps can even run on the CLR because of IKVM (https://www.nuget.org/packages/IKVM).

Good luck at using pointers in Java.