Not not mention...
(Downvotes at the ready :D)
What else Jacking and Jilling something means...
Andriod always seems wa*ky to me, so maybe it ok.
Google has come up with new Android compilers, spotted in the latest preview SDK by Eric Lafortune at Saikoa. The compilers are in the Android SDK 21.1 and are currently called jack.jar and jill.jar. They are not enabled by default, but require the directive “useJack true” in the configuration file for the gradle build tool. …
We had Janet & John. And boy were they dull...
I suspect my reading was only rescued by Willard Price's animal Adventure books. Hal & Roger are exploited by their parents as cheap (and very under-aged) labour in very dangerous jobs. But instead of going to social services, end up populating their father's zoo with animals, while avoiding kidnappers, murderers, or just getting eaten.
Lollipop defaults to use ART which does ahead of time compilation on apps. So it already happens. If there are performance issues it is likely nothing to do with the apps and more likely to do with the services they hit, or the kernel in some way (scheduler, IO etc.)
ART should and (does in my experience) result in faster application performance. Instead compiling the dalvik byte code when the app launches, it's already compiled so the app launches faster and is already running natively. Aside from being faster it saves battery because compilation is a 1-shot process instead of every time the app is launched from cold.
They are native binaries but that's not quite the same as what you might get with entirely native code – it depends on how good the ART compiler is – this is the sort of thing that Intel has to deal with for apps that won't run on Android x86.