Yes, you are right, for many applications it may not be that critical. It rather reflects my own disappointment with the fact that whereas modern Nokia phones meet my real-time requirements with Java ME and offer satisfactory performance for users without any need to mess with native code, the speed loss of a factor 5-10 under Android means that my app isn't really usable under Android for some time to come. AFAIK there's nothing on the public Android roadmap either concerning a JIT compiler, or a native vector processing library with an Android API, and an ETA for the NDK is still missing, so there is currently not much point in planning ahead here when one needs more performance while maintaining CPU independence at the coding level (say for ARM and x86).
On Apr 1, 10:28 pm, dm1973 <david050...@gmail.com> wrote: > Just remember that for a lot of applications most of the time is > spent calling native routines not executing java code. It isn't great > for battery life but it isn't as bad as you first think since in a lot > of apps, you spend almost all your time in wait loops so the CPU drain > isn't as important as screen and radio power management. > > Not having the most advanced VM in the world is not a show stopper to > me in a 1.0 product. It would be nice to see a roadmap explaining > where google/OMA is going. But I also understand that maybe this info > is only shared with OMA partners. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
