By now you've probably heard about ART and how it will improve the speed and performance of Android, but how does it actually perform today? The new Android Runtime promises to cut out a substantial amount of overhead by losing the baggage imposed by Dalvik, which sounds great, but it's still far from mature and hasn't been seriously optimized yet. I took to running a battery of benchmarks against it to find out if the new runtime could really deliver on these high expectations.
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.
We know Blackberry isn't the most popular name around here, but it is a name that continues to pop up at some interesting times. Developers, in particular, may remember when the company - then known as RIM - launched Playbook OS 2.0 with the ability to run specially packaged apps developed for Android 2.3.3. Since that time, events and promotions have been run to encourage developers to bring their apps to the platform, but the aging requirement to target Gingerbread has become a burden.
I know. You thought Flash was long gone. You mourned the relationship and moved on. Having made peace with the past and exploring a bright future, you were ready to start a new life with HTML5. Now, thanks to Mozilla, your ex has come calling, bringing back all those old memories. But enough with the metaphors. The organization behind Firefox announced Shumway, an open SWF runtime project, today. With this, the company hopes to bring compatibility for Flash content back to the web, particularly on mobile.