Linked by Thom Holwerda on Thu 31st May 2012 21:41 UTC
Thread beginning with comment 520349
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[8]: Comment by shmerl
by phoenix on Fri 1st Jun 2012 16:32
in reply to "RE[7]: Comment by shmerl"
And ... the problem is?
Android is not Java.
Dalvik is not Java.
Can you use Java syntax to write Android programs? Sure. But it's not Java.
Can you use Java libraries in Android programs? Sure. But it's still not Java.
Nowhere has Google ever claimed that Dalvik is Java. So how is it fragmenting Java?
You can't run Dalvik bytecode on JVM and vice versa.
Did you not read the description? You can run JVM bytecode on Dalvik by converting it to Dalvik bytecode before installation.
So you're at least half wrong by saying "and vice versa".
You can't run Dalvik bytecode on a proper JVM, but due to the ability to convert Java bytecode to Dalvik, a developer can write and compile Java into JVM bytecode and be able to distribute just the JVM version and end up with something that runs in a JVM and can be made to run on Dalvik.




Member since:
2010-06-08
The bottom line - runtimes are incompatible. You can't run Dalvik bytecode on JVM and vice versa.
Edited 2012-06-01 15:02 UTC