7 ms·
Android kept the Java language, and pitched out the JVM. Does this seem backwards to anyone else?
by megaduck 17y ago
Android kept the Java language, and pitched out the JVM.
Does this seem backwards to anyone else?
- twopoint718 17y agoIt does. What would be the rationale for this? Is it just that they didn't want the standard Java ME runtime?
- nswanberg 17y agoHere is some speculation on why: http://www.betaversion.org/~stefano/linotype/news/110/ http://www.betaversion.org/~stefano/linotype/news/110/
- jeremychone 17y agoVery interesting article on a possible explanation. Google is also doing this with GWT.
- twopoint718 17y agoIt looks like this is good news for anything that targets the JVM though, as it looks like the path to Dalvik bytecode is: .java -> [javac] -,-> .class -> [dx] -> .dex / ??? ------------' Has anyone done this, with Clojure, for example?
- rictic 17y agoThe most novel thing I've heard about Dalvik is their zygote technique for minimizing app startup time. The zygote is is a Dalvik process that's loaded and ready but for the actual bytecode it will need to run. To start a process it first makes a fork of the zygote, which allows for more shared memory and a more expensive initial setup time for the zygote without any penalty when creating new Dalvik processes. I dunno if this technique necessitated writing their own VM however.
- wmf 17y agoDalvik is basically a JVM. A lot of Java bytecode (including non-Java languages) will run on Android.