> True but it would be even simpler just to get the JIT for Dalvik so we can > use the same language everywhere.
I agree, and I prefer a good JIT compiler over everything else. My main concern is how long it is going to take before we find a decent Dalvik JIT compiler on the majority of Android phones. Although I personally cannot judge what time frame is realistic, or how priorities are set, the impression I got so far is that it might take years before we have something approximating Sun's Hotspot technology. Another possible advantage of Javascript over C (through JNI/NDK) could here be that its security issues are pretty well understood and managed through years of exposure on the Internet, while communicating with Javascript may also further ease development of fancy and highly interactive web-based augmented reality applications, which in turn is good for... search. Hmm, I happen to know of a company with some interest in just that. It all looks like V8 can offer the shortest path to a platform- independent performance boost for Android applications. Regards On May 23, 2:19 am, Cedric Vivier <[email protected]> wrote: > On Sat, May 23, 2009 at 5:33 AM, blindfold <[email protected]>wrote: > > > whereas Dalvik bytecodes are always only run through an > > interpreter. In looking for means to accelerate Android programs, I > > would greatly prefer a platform-independent JIT compiler over any > > platform-dependent solutions such as the NDK/JNI where different > > distribution packages must be generated for different target platforms > > based on ARM, x86, MIPS, whatever: a maintenance, packaging and > > distribution headache. > > +1 > By the way why Android still has no JIT (or Ahead-Of-Time JIT) at this time, > is it because of a technical issue or just lack of time/resources?? > > Looks like it is one of the main current drawbacks of the platform right > now..and potentially lessens battery life (ie. more code have to be executed > to run the same thing in the end). > > > > > Typically, math code looks syntactically very similar in Java > > and Javascript, such that there is little effort involved in re-coding > > one's time-critical sections in Javascript. > > True but it would be even simpler just to get the JIT for Dalvik so we can > use the same language everywhere. > > Cheers, --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
