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

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 576329
To read all comments associated with this story, please click here.
RE: Dalvik, ART, ...
by dragos.pop on Thu 7th Nov 2013 10:52 UTC in reply to "Dalvik, ART, ..."
dragos.pop
Member since:
2010-01-08

...it is *still* Java, though :/

Switching to Erlang would improve things, forcing everyone to message passing, concurrent processes with no semaphore/mutex, massive network parallelism, etc

Kochise



Well the programming language is still java, not the run-time.
Switching to Erlang would be disruptive and lower the number of developers.
Everybody has it's favorite programming language, and they have very good reasons to, but does it apply to others?
If I wore Google I would encourage people to develop alternative languages for there SDK.

Reply Parent Score: 5