4 ms·
Well, Google have officially dropped Dalvik (i.e. a JVM) in favour of ART (pre-compilation to native code). This is the perfect opportunity to open up the platf
by Benjamin_Dobell 12y ago
Well, Google have officially dropped Dalvik (i.e. a JVM) in favour of ART (pre-compilation to native code). This is the perfect opportunity to open up the platform to a plethora of new programming languages without needing to worry about being JVM compatible. Instead an LLVM back-end can be produced to compile straight down to ART ABI compatible native code.
- badlogic 12y agoART is still heavily bound by many JVMisms. All of the framework code is Java as well, so whatever you intend to use with ART has to have some understanding of the Java world as well.
- mike_hearn 12y agoART is a JVM, it's just not a just-in-time compiling JVM. The JVM is fine for multiple programming languages, as Kotlin nicely proves. And Kotlin targets Java 6 so it should work fine on Android, even though now Android supports Java 7 language features. The missing parts are the Java 7 API's: unfortunately the class library, being based on Apache Harmony (a dead project) does not move forward on Android. However this does not have any effect on Kotlin.
- pjmlp 12y agoART uses DEX as intermediate format and the framework code is still Java based anyway. Compiling to native code does not change the fact the languages need to be able to interact with ART ABI, which requires Java semantics. This is no different from the old days when OS had multiple system programming languages and C ABI != OS ABI.