Re:Nodyn – Node.js for the JVM
by pcwalton on Wednesday February 26, 2014 @10:40PM
(#7310256)
Even then it's not that easy. A non-optimizing C compiler will have a hard time beating the JVM's slew of optimizations.
[ Parent
| on HN ]
Re:Nodyn – Node.js for the JVM
by erichocean on Thursday February 27, 2014 @12:50AM
(#7310608)
A non-optimizing C compiler
Is there a C programmer on the planet that does production builds with a non-optimizing compiler? How is your comparison even remotely relevant to the GP?
Re:Nodyn – Node.js for the JVM
by bruceboughton on Thursday February 27, 2014 @05:30AM
(#7311402)
I believe the GP is referring to writing a non-optimising compiler in C. Not compiling your C code using a non-optimising compiler.
That's mostly true, but just like managed languages can leverage JVM, native languages can leverage LLVM.
The advantage of going the native route is that it gives you improved observability and post-mortem. The JVM is a VM (Java's) inside a VM (the OS's), and that additional layer doesn't come for free.
Most commercial JVMs also have native compilers for Java, and there are a few projects to run JVMs directly on top of hypervisors without OS in the middle.
Some of those are actually LLVM frontends.
I'm referring to the open Hotspot which almost everyone uses, not some specialized JVM products which are closed-source. You do bring up an interesting point though.
As for the type of hypervisors you're referring to, those things are effectively half-baked operating systems. That's why something like KVM is better -- you're not pretending to be a non-OS while slowly reinventing a wheel that the *nixes have and always will do better.
I think we're beginning to wander massively afield though! :)