3 ms·
Indeed, there's quite a few choices out there, especially for specialisms (large heaps, real-time applications etc). Not only that, but it's also good to note
by joncrocks 12y ago
Indeed, there's quite a few choices out there, especially for specialisms (large heaps, real-time applications etc).
Not only that, but it's also good to note that Android != Java. It's best described as Java-like, in that there are some libraries/features in Java that aren't supported in Android, so it's a bit of a misnomer to describe it as a full JVM.
- chc 12y agoCouldn't you say the same of J2ME?
- joncrocks 12y agoTrue enough. I might have mis-stated things slightly. I think the only difference might be the portability. Android takes 'Java' code and outputs 'android machine code' that can/does only runs on an 'android machine' (I think). Compiled Java in theory should run the same on any JVM, as it's virtual machine code, and the 'machines' use the same set of defined instructions.
- pjmlp 12y agoThe same applies to other JVMs in the embedded space. For example, J9, http://www-01.ibm.com/software/wireless/wece/features.html http://www-01.ibm.com/software/wireless/wece/features.html ==> jar2jxe: A utility for converting Java class and archive files to the native J9 JXE file format. Or JamaicaVM Builder https://www.aicas.com/cms/sites/default/files/jamaicavm_6.3_manual.pdf https://www.aicas.com/cms/sites/default/files/jamaicavm_6.3_... The big difference between these JVM and Dalvik, is that they are certified JVMs, whereas Google tried to workaround the licensing issue for embedded Java deployments.