2010/11/26 Cédric Beust ♔ <[email protected]> > > On Fri, Nov 26, 2010 at 12:52 AM, Fabrizio Giudici < > [email protected]> wrote: > >> As a mere technical discussion here, it's interesting to learn that >> probably Dalvik has no technical justification for its existence, other than >> some legal points. > > > This is incorrect. > > Dalvik was created first and foremost for technical reasons. Dan explained > some of these in this > post<http://android-developers.blogspot.com/2010/05/dalvik-jit.html>, > but in a nutshell, the traditional JVM model is not well suited for embedded > development and Dalvik addresses this by focusing on very selective > compilation, aggressive memory optimizations, power consumption awareness > and a strong emphasis on multiprocesses and VM sharing. >
Indeed, the (micro-)benchmarks used in the original article don't necessarily relate to real-world mobile applications. And interestingly the Dalvik VM beats the JavaSE Embedded VM in all the "Strings" tests... so it's not all one-sided. -- Cheers, Stuart > -- > Cédric > -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
