Timeline for Dalvik VM vs. ART (Android Runtime): Impact for end-users?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 2, 2013 at 20:21 | history | edited | Flow | CC BY-SA 3.0 | Improved answer, clearified some points |
| Dec 2, 2013 at 20:19 | comment | added | Flow | Excellent answer. I took the freedom to improve it a bit. But I don't agree with the last paragraph: ART does not increase fragmentation: If ART is considered production ready, it shouldn't matter if your App is run by Dalvik or ART, both use the same .dex format as starting point. Only that ART does AOT compile the .dex to native code. | |
| Dec 2, 2013 at 20:16 | history | edited | Flow | CC BY-SA 3.0 | Improved answer, clearified some points |
| Nov 13, 2013 at 14:31 | vote | accept | iOS Enthusiast | ||
| Nov 11, 2013 at 13:22 | comment | added | Izzy | Maybe two facts are worth noting along: ART's AOT results in apps using 20..25% more storage compared to DEX. Plus tests on a Nexus-5 I've read didn't show any differences in subjective speed nor battery endurance. Both will certainly improve, considering ART in KitKat being just a developers' preview and compatibility check (which e.g. WhatsApp failed). So I second Sachin's conclusion: It's not yet good for end-users. | |
| Nov 11, 2013 at 12:25 | history | edited | iOS Enthusiast | CC BY-SA 3.0 | added 9 characters in body |
| Nov 11, 2013 at 12:19 | history | answered | iOS Enthusiast | CC BY-SA 3.0 |