To view parent comment, click here.
To read all comments associated with this story, please click here.
[q]show what ?
Speed disaster? Come on, please be correct. Java was slow in the beginning of its release. Current JIT compilers are as fast as C++ / native code or even faster in some cases.[q]
So that's why OpenOffice is too fast, and Eclipse is too fast, and netbeans is too fast and JavaEE apps are tooooooooo fast
The major problem with Java/.Net (or most VMs for that matter) is not its speed, but rather the high memory requirements for initial JIT compiling of bytcodes whenever they are loaded and the GC tuning that is required to develop performance apps with it. A way around the JIT memory requirement is to do AOT. This would however not solve the GC problem and make your Java app non WORA.
The J2ME JVMs tend to interpret code when there isn't enough RAM to JIT compile classes. Some J2ME VMs, like the IBM J9, can accept AOT compiled classes that do not have the JIT overheads, but would only run on CPUs they were targeted for.
-Ad




And Eclipse was waaay faster than KDevelop when I last checked it...
Member since:
2007-03-23
Anyway, I don't like Java and its speed disaster.
Some years I heard about an OS written in Java, still alive ? XD
C++ is for robust things, Python is for prototyping this is the best combination !
Speed disaster? Come on, please be correct. Java was slow in the beginning of its release. Current JIT compilers are as fast as C++ / native code or even faster in some cases.
Why do you think NASA is using Java instead of C++? Because of pointer bugs. Its not reliable enough.