I know some people will not like what i'm going to write here, So should user's use ART runtime? No! .



First let's talk about Google-in-Go (Go), Go is the language from Google and Android is the mobile OS from Google. So far there is no Android SDK for Go, and Go doesn't support JNI so switch to ART sound a good idea since ART can compile to two banckends "Quick" and "Portable" "JIT and LLVM".

If it's LLVM, that pretty much opens the door for running Native Client apps on Android, and possibly even merging Android with ChromeOS, right?



Go 2.0 can handles 64-bit much better than 32-bit and 64-bit applications is Google next target. Porting Android's Dalvik to 64-bit would be like converting a subcompact econobox into an all terrain SUV. It would make far more sense to throw it away and start from scratch, where scratch is, for Google, ART + Go



Why Go?

Go is fast, Go launguage is bundled with high quality libraries, Go is from Google!

.

Now, FlexyCore. Flexycore's most prominent product is "droidbooster," /generating heavily optimized ARM binaries/ an app that will make your Android device run 10x faster and increase battery life... sound familiar? "ART"

FlexyCore was development outside the public eye, And now Google acquisition the company for $23.1 million!, Google statement was: The FlexyCore team has strong expertise in building software to optimize Android device performance, and we think they’d be a great fit with our team.



Let's talk again why not to use ART now?

Android is implemented in Java. Pretty much all of Google Play Services is implemented in Java.

That means android can rely less on the fact that graphics and guts of many UI widgets are native code under a thin layer of Java. Android was always a Java OS. So you will not find any different if you switch to ART unless you are doing significant computation in your own app, a synthetic benchmark will vastly over-emphasize the impact of a better JIT. ART is there only so Google can obtain early feedback from developer's and partner's.





Sources:

(ycombinator - arstechnica - paradigmx - Android)