Linked by Thom Holwerda on Thu 31st May 2012 21:41 UTC
Legal And thus, it ends. Despite a never-ending stream of doom and gloom from Oracle/Microsoft-funded 'pundits' regarding Google and Android (six hundred billion trillion gazillion eurodollars in damages!!1!), judge Alsup has just squashed all of Oracle's chances with a ruling that is good news for those of us who truly care about this wonderful industry: APIs are not copyrightable. Alsup: "To accept Oracle's claim would be to allow anyone to copyright one version of code to carry out a system of commands and thereby bar all others from writing their own different versions to carry out all or part of the same commands. No holding has ever endorsed such a sweeping proposition." Supreme Court, Ellison?
Thread beginning with comment 520349
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Comment by shmerl
by shmerl on Fri 1st Jun 2012 15:01 UTC in reply to "RE[6]: Comment by shmerl"
shmerl
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

Reply Parent Score: 2

RE[8]: Comment by shmerl
by phoenix on Fri 1st Jun 2012 16:32 in reply to "RE[7]: Comment by shmerl"
phoenix Member since:
2005-07-11

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?

Reply Parent Score: 3

RE[8]: Comment by shmerl
by kwan_e on Fri 1st Jun 2012 17:14 in reply to "RE[7]: Comment by shmerl"
kwan_e Member since:
2007-02-18

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.

Reply Parent Score: 3

RE[9]: Comment by shmerl
by shmerl on Fri 1st Jun 2012 18:59 in reply to "RE[8]: Comment by shmerl"
shmerl Member since:
2010-06-08

Converting it during installation is not a good method, more interesting solution would be to convert it at runtime (what different emulators do). But it adds overhead. The whole point of compatibility is to avoid such things. But well, in this case they diverged.

Reply Parent Score: 2