3 ms·
Because it stinks, technically: JVM (even on mobile devices) was never designed to be memory efficient. Dalvik is, big time. I would even say that we all need "
by old-gregg 16y ago
Because it stinks, technically: JVM (even on mobile devices) was never designed to be memory efficient. Dalvik is, big time. I would even say that we all need "Dalvik for desktop" as JVM, with its enormous startup lag and memory appetite is nearly useless outside of data centers.
Also, Google is betting on mobile big. And if you want to play in that space you better have your own platform and not depend on someone else's licenses. I think it only proves that it was the right move: JVM is now owned by assholes and being in court for patent "infringement" with them is still a lot better than betting the company future on the OS based on a platform owned by assholes.
- RodgerTheGreat 16y agoIt's difficult to find hard numbers for Dalvik, but the KVM[1] (Sun's JVM for mobile devices) was designed for memory efficiency and can operate in roughly 128kb of working RAM. [1]http://discolab.rutgers.edu/classes/cs672-fall00/j2me/Appendix1/CLDCappendix-intro.pdf http://discolab.rutgers.edu/classes/cs672-fall00/j2me/Append...
- dagw 16y agoHowever it achieves that memory use by targeting J2ME not J2SE which is what Dalvik uses. J2ME is a very limited Java target at much more limited phones and not really something suitable for writing cutting edge apps for the next generation of smartphones.