Posted Friday 26th June 2009 22:51 GMT
If I understand correctly, this is a novel definition of native code. By definition, native code is executed by the processor. However, it seems that this native-ish code is still going to be executed by the virtual machine, or will the virtual machine, upon encountering it, pass it verbatim to the processor for execution?
-dZ.
Posted Friday 26th June 2009 23:19 GMT
...or did anyone else read that as "Dalek VM" at first?
Posted Saturday 27th June 2009 15:19 GMT
I assume the reg screwed up the meaning, and in fact what happens is that a java app running on the VM can call into native C/C++ libraries that get compiled to ARM/Thumb/whatever..
Posted Saturday 27th June 2009 15:19 GMT
The android platform is looking more attractive, I wonder how long until we'll be able to merge native and non native code in the same application?
OT:
The reporter has made a grammatical error in paragraph 4, line 1. There is the substitution of 'there' with 'their'.
This post has been deleted by its author
Posted Sunday 28th June 2009 03:33 GMT
I love embedded C/C++ development. I love java development. But I've never seen anyone merge the two paradigms successfully. I hope that they can make it work but I'm skeptical.
Posted Sunday 28th June 2009 23:48 GMT
I'm sure I heard a nice man from Google call Dalvik "Native java", I missed what he said next because I was trying to get my head around that contradiction in terms.
Posted Sunday 28th June 2009 23:48 GMT
Java - Has had the ability to interface with native libraries for a long long time.
ARM - Some ARM chips can actually execute Java bytecodes..
Big whoop.
Posted Monday 29th June 2009 08:57 GMT
Android looks more and more like lock in to me. I feel the Linux world is not going to benefit much from Android, and Android is only going to benefit a little from Linux.
The best I can see coming out of it is that Dalvik turns out to be a better ./Net/Mono without the MS dangers. Which could only be a good thing, finally taking the Java dream of write once run anyway main stream. Being able to replace bottle neck VM code with native code can only be a good thing, it just needs to be able to be compiled on other platform as easily as possible.
Moblin looks more to my taste, full little Linux (including a X server), so can run anything I want, providing it compiles for ARM. If Dalvik is truly open, it could also run on Moblin.
Back to the article
