4 ms·
Google made ART as Dalvik 2.0. The ecosystem evolves, the hardware evolves, the OS and its requirements evolve as well, so the runtime must follow. I don't
by on_and_off 12y ago
Google made ART as Dalvik 2.0.
The ecosystem evolves, the hardware evolves, the OS and its requirements evolve as well, so the runtime must follow.
I don't think it changes anything to the JNI bridge. I can be wrong, but I don't think that it is a main area of focus for Google.
This being said, Google is moving to a more pluggable build system (Gradle and its plugins) and runtime.
Is it a nice benefit and only a side effet ? maybe, maybe not. Time will tell if Google want to move to Kotlin/Go/Dart/Scala/Rust/insert your pet language here.
The official line is that moving the core libraries to something else would be an enormous amount of work and at the moment, they don't see the benefits outweighing the cost.
It is possible that Google is secretly working on some other language, it is also possible that they intend to stick with Java and make it better instead (cue Dagger 2, Guava, AutoValue, ...).