Android replaces Dalvik with ART
richard.bair at oracle.com
Thu Nov 7 14:54:12 PST 2013
I *really* doubt this has anything to do with the legal battle, it is much more likely to be the fact that Dalvik is painfully slow. Using an AOT compiler is not actually changing anything with regards to the fact that their development language is Java with a non-TCK compliant set of class libraries. I read a really horrible article today that was factually incorrect with regards to the technology (claiming that Dalvik executed Java byte-code!). I'm so used to reading completely bogus stuff in the press (about subjects that I know!) that I really wouldn't recommend believing the stated motivations unless we get somebody on record.
Besides which, AOT seems like a fantastic way to go, technically, so I don't think it really needs any more reason for it :-)
On Nov 7, 2013, at 11:24 AM, Tobias Bley <tobi at ultramixer.com> wrote:
> after we reached the goal to use JavaFX on Android via Dalvik, Google announces the successor of Dalvik, called ART (Android Runtime). The start to move because of the legal issues with Java and Oracle….
> The question is now: How to use JFX on Android on top of ART? As I posted in my blog.software4java.com, we need a own JVM to embed in Android apps.
> Best regards,
More information about the openjfx-dev