Recommended Posts

?Dalvik is dead?: Google replaces Dalvik with ART in AOSP master branch

 

Google has just pushed changes to the master branch of AOSP that remove the aging Dalvik virtual machine and replace it with ART.

 

It?s been a long way coming, but ART is finally taking the reins from the venerable Dalvik as Android?s default virtual machine. Standing for Android Runtime, ART was introduced in Android 4.4 KitKat as an experimental feature that users could activate from Developer Options. At the time, Google made it clear that ART was still a work in progress and that issues with various apps were to be expected.

 

One of biggest differences between ART and Dalvik is that ART pre-compiles bytecode when the app is installed, unlike Dalvik, which requires Just-in-Time compilation, which happens when an app is launched. Through Ahead-of-Time compilation, ART cuts down app launch time in half, according to Google, though users are not likely to notice a huge effect on performance. More about ART vs Dalvik here.

 

Now it looks as ART is finally ready for primetime. As spotted by XDA Portal, two commits made to the Android Open Source Project (the open source base of Android) remove Dalvik and replace it with ART. The two changes were made by Google senior software engineer Brian Carlstrom to the master branch of AOSP.

 

The first commit removes Dalvik components from the project, while the second switches to the new Android Runtime.

 

art-commit-aosp-1-710x298.png

 

art-commit-aosp-2-710x298.png

 

The first signs that Google was readying to switch to ART emerged in January, when the new runtime was made the default option. Back then, Dalvik was kept as a fallback option, but following today?s commits that?s no longer the case.

 

So, what does that mean for the average user? Changes in AOSP are added to stock Android (and later to OEM implementations) through system updates. While we can?t speculate when it will happen, the next version of Android will definitely make the move to ART. With Google I/O next week, it?s tempting to see the switch as a sign of something new coming, but that may be just wishful thinking.

 

ART still poses problems to a few apps, most notably the Xposed framework. However, developers will have plenty of time to get their apps up to snuff before the change finally begins trickling down to users.

 

Source: Android Authority

Link to comment
Share on other sites

Hmm, I'm assuming this will get announced at I/O. Hopefully all the app devs. are responsive to the switch

Link to comment
Share on other sites

This could also lesson damage if Oracle wins it's lawsuit (on future products). 

Link to comment
Share on other sites

Very good indeed!  :D

 

But as the article says, Xposed in particular does not work. I haven't been keeping up with the news, but it has been ages now and ART is still not supported by Xposed.  :no:

Link to comment
Share on other sites

Very good indeed!  :D

 

But as the article says, Xposed in particular does not work. I haven't been keeping up with the news, but it has been ages now and ART is still not supported by Xposed.  :no:

 

Well it will be soon, they said they wouldn't make it ART-compatible until it was out of testing. Something to do with not having the time to maintain both a dalvik and ART version I guess.

Link to comment
Share on other sites

Well it will be soon, they said they wouldn't make it ART-compatible until it was out of testing. Something to do with not having the time to maintain both a dalvik and ART version I guess.

 

Yeah, I just read about it here: http://www.xda-developers.com/android/breaking-next-major-version-of-android-to-finally-remove-dalvik-and-set-art-as-default/#comment-1443524068

Link to comment
Share on other sites

Is this going to be Android's Vista? Developers knew it was coming, had the beta or test versions available and yet come release most were "not ready" and look what it did to Vista's reputation

Link to comment
Share on other sites

Is this going to be Android's Vista? Developers knew it was coming, had the beta or test versions available and yet come release most were "not ready" and look what it did to Vista's reputation

anything that pulls android away from its dependency on java can't be all bad  :yes:

Link to comment
Share on other sites

This could also lesson damage if Oracle wins it's lawsuit (on future products). 

I'm not sure this affects it, as that is about syntax and such, and the language is the same. Just a different runtime/compiler.

Link to comment
Share on other sites

anything that pulls android away from its dependency on java can't be all bad :p

It's still Java code isn't it, just a more intelligent runtime? Sounds like it borrows some ideas from dotNET.
Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.