4 ms·
Google's Dalvik VM is specifically designed for mobiles. Presumably a lot of the engineering trade-offs made in light of that would make Dalvik relatively weak
by jsankey 16y ago
Google's Dalvik VM is specifically designed for mobiles. Presumably a lot of the engineering trade-offs made in light of that would make Dalvik relatively weak on servers. So I'm not sure Dalvik would be a great starting point for Google to fork Java.
Having said that, Google are heavily reliant on the Java platform, so they must have at least considered how they can protect the platform if necessary. Could they fork OpenJDK? Or at least support a fork? They certainly have the resources to do it, and Oracle's early moves don't bode well for a cooperative solution, so I wouldn't be surprised. Perhaps they will use the current litigation as a test re: the possible patent issues, although by the time that is resolved it may be too late to make a move...
- wmf 16y agoGiven that Dalvik is designed to run multiple Java processes with low memory overhead and fast startup, it might actually be pretty great for PaaS like, say, App Engine. That's just speculation, though.
- bad_user 16y agoI don't think there's anything in Dalvik's bytecode that's specific to servers, and so they could have 2 versions of the VM: one for mobile phones, and one for the desktop/server. If they'll release specs for Dalvik, make it a standard somehow, I'm pretty sure Apache will help.
- deleted 16y ago[deleted]