Linked by Thom Holwerda on Thu 7th Nov 2013 10:11 UTC, submitted by nej_simon

It's fair to say that Android went through some chaotic years in the beginning. The pace of development was frantic as the operating system grew at an unprecedented rate. An as-yet undetermined future led to decisions that were made to conform to existing hardware and architectures, the available development tools, and the basic need to ship working code on tight deadlines. Now that the OS has matured, the Android team has been giving more attention to some of the components that haven't aged quite as well. One of the oldest pieces of the Android puzzle is the Dalvik runtime, the software responsible for making most of your apps run. That's why Google's developers have been working for over 2 years on ART, a replacement for Dalvik that promises faster and more efficient execution, better battery life, and a more fluid experience.

This will be one of the defining changes in Android over the coming years. Android 5.0, perhaps?

Permalink for comment 576399
To read all comments associated with this story, please click here.
RE[5]: Dalvik, ART, ...
by snowbender on Thu 7th Nov 2013 19:53 UTC in reply to "RE[4]: Dalvik, ART, ..."
Member since:

Personally, I wish Java with all its 'ClassNotFound' crapware would die a particularly nasty death.

Why the hate? Why should it die?

It seems a bit naive to call it "ClassNotFound crapware", since a ClassNotFound error would not be a language "feature" but a programmer error.

If you don't like the Java language, then don't use it. In my opinion it's one of the strongest languages for development of backend systems, or maybe not the Java language itself, but the whole eco system of the JVM, the application servers, and all the languages that run on top of the JVM (ranging from Java, Scala, Clojure up to JRuby).

Reply Parent Score: 5