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?

Thread beginning with comment 576508
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Geez
by _txf_ on Sat 9th Nov 2013 01:11 UTC in reply to "RE: Geez"
_txf_
Member since:
2008-03-17

Its actually a little more involved than your run of the mill AOT.


What specifically makes it more involved than AOT ?

Also I don't think anyone here is suggesting it is new and innovative, just that it is new for Android and is interesting.

Edited 2013-11-09 01:13 UTC

Reply Parent Score: 3

RE[3]: Geez
by Nelson on Sat 9th Nov 2013 02:19 in reply to "RE[2]: Geez"
Nelson Member since:
2005-11-29

It defers the final lightweight compilation step which takes a lower level MDIL (with complex optimizations performed) and replaces architecture agnostic façades with specialized assembly.

This last step takes 75% less time than install time AOT because the heavy lifting as already been done with cloud compute turning MSIL to MDIL.

Microsoft calls it cloud compilation, and apparently they have a patent on it.

Reply Parent Score: 3

RE[4]: Geez
by moondevil on Sat 9th Nov 2013 07:11 in reply to "RE[3]: Geez"
moondevil Member since:
2005-07-08

It defers the final lightweight compilation step which takes a lower level MDIL (with complex optimizations performed) and replaces architecture agnostic façades with specialized assembly.


The only thing that they defer for installation time is linking.

MDIL is native code with symbolic names for jump targets and method invocations kept on place.

It is not much different than a normal native DLL.

Reply Parent Score: 3