What Android 2.0 and the new Motorola Droid mean for Android
journal.markbao.com
journal.markbao.com
There are several things wrong with that:
* JIT'ed Java, in this day and age, is actually quite fast.
* However, Android doesn't really run on 'Java', but on Dalvik, their own VM, which probably does make it a bit slower until such time as they get around to giving it a kick in the pants and including a JIT or something else to speed it up.
Making change as soon as I have access to a non-BlackBerry device (which is admittedly also Java.)
It will also be interesting to see how the performance will be influenced by the fact that all the programs will be Java. On the desktop/server you can get away with a memory hungry Java app to gain speed, but on a device...
Google didn't have much choice with programming languages and API: Nokia bought Qt, .NET belongs to Microsoft, and that left them with Java. They should probably add a Python interpreter if they haven't already. Nokia has had reasonable success with this approach.
(citation needed)
Dalvik seems to work just fine. It also helps that Android doesn't use libc but their own custom-written version (bionic) that has a lot of the standard stuff (strcmp, memcpy) hand-written in ARM assembly. What does the JVM do?
I wouldn't call it