On Nov 26, 9: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.
Dalvik is optimized for class sharing between VM instances, something "regular Java" hasn't achieved so far (maybe after modularization in JDK 8). Imagine ten Android apps running at the same time, and they all would load their own set oft the same Android SKD collection / network / file classes... This is especially important on memory- constrained devices like phones. Internally, there's one VM instance (called "Zygote") launched at boot time that loads all the core classes. Other VMs are spawned off of this and use these core classes. More in this PDF on page 5: http://davidehringer.com/software/android/The_Dalvik_Virtual_Machine.pdf -- 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.
