Emergent: Oracle's behavior re Java

[Bruno Girin]

On Sat, 2010-08-14 at 03:12 +0530, Manish Sinha wrote:
<snip>
> They are going after Google as they think they can make a huge amount of 
> money since Google has deep pockets. If Google bends, then the patent 
> deals would be a huge monetization for Oracle.
> 
> As I said, DVM is not JVM and has different instruction set. Oracle 
> needs to prove that their patents are being infringed in DVM. I don't 
> get about fragmentation. The dev end code is same, the VM is different. 
> The dev cares more about the code *if* he knows that it's 
> write-once-run-anywhere.

Well no, the code is not the same: DVM doesn't ship the whole of the
standard API and adds bits of its own, in particular the UI packages.
Also, DVM is the only JVM for which a dev has to compile specifically
because the byte code is different. For any other implementation of the
JRE, the byte code is the same so you can compile your app and ship a
jar file rather than source code and it will run.

>From a development point of view, if you want to create a Java app for
mobile, you do have to target two environments: JME and Android; hence
the fragmentation.

Anyway, I'm not saying that Oracle is right or wrong in doing this, I'm
just trying to understand the motivation behind it.
 
Bruno