Advertisement
Front, Kernel, Security, Distributions, Development. See your byline here on LWN.net.
| |||||||||||||
|
| |||||||||||||
Can it be ported back to non-phone devices?Can it be ported back to non-phone devices?Posted Nov 13, 2007 17:30 UTC (Tue) by clugstj (subscriber, #4020)In reply to: Can it be ported back to non-phone devices? by daney Parent article: Dalvik: how Google routed around Sun's IP-based licensing restrictions on Java ME (Betaversion)
Please read the article. The incompatibility is not for a technical reason, it is for a legal reason. It allows them to make something that looks like Java ME, but isn't controlled by Sun.
(Log in to post comments)
Can it be ported back to non-phone devices? Posted Nov 13, 2007 17:34 UTC (Tue) by daney (subscriber, #24551) [Link] I did read the article. I just think the stated reason for the imcompatiblilty is bogus.
Can it be ported back to non-phone devices? Posted Nov 13, 2007 18:15 UTC (Tue) by sayler (subscriber, #3164) [Link] Or at least not the "only" reason -- or perhaps a happy side-effect..
Can it be ported back to non-phone devices? Posted Nov 14, 2007 9:09 UTC (Wed) by massimiliano (subscriber, #3048) [Link] Well, I've been told by a friend that works on JVMs at Nokia that the technical choices made in Dalvik are really important (and smart). For instance, the Dalvik file format allows direct execution mapping the file into memory (think mmap), without the need to create a truckload of data structures just to be able to load the file. Compare this with the Java "jar" and "class" formats, and think what it means for startup time... Of course the "political" reasons apply as well, but strictly speaking they are more economical (avoid licensing fees) than political, so even in this sense the choice seems very pragmatic.
|
|
||||||||||||