Linked by Thom Holwerda on Thu 14th May 2009 15:39 UTC
Permalink for comment 363759
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2005-07-06
come on - read up on things!
There is no pure C/C++ OS either - they all need (some) ASM (I am not aware of register level access from within C - but I could easily be wrong).
Java has no way to execute asm code directly, however it can execute native code via JNI.
Thus you need a VM + JNI to create a Java OS - which is done by the JNode project: http://www.jnode.org/
However, all this aside - creating an OS in a language is not a requirement to prove its performance.
Java IS slower than C/C++ - however, it all depends on the compiler. Java has Hotspot which can do RUNTIME (jit) optimization whereas C/C++ has Ahead of Time compilers/optimizers. This means that c/c++ code will typically be optimized from the beginning whereas java needs some investigations to create the optimum path. This means that during an applications life-span it should (and often do) perform faster in Java.
This is basically what the LLVM project is doing for c/c++ - which means that c/c++ should get much faster, and gain some of the Java-jit benefits.