Mysterious Android codebase commit
This diff is more explicit about what's going on:<p><a href="https://android.googlesource.com/platform/libcore.git/+/aab9271edee6cc8b4dd460977cad65efe52d16b0" rel="nofollow">https://android.googlesource.com/platform/libcore.git/+/aab9...</a><p><pre><code>    Change dependency from libart -> libopenjdkjvm.
</code></pre>
There are also diffs adding lambda support, tweaking various classes for compatibility with applications that use reflection to access internal capabilities, and fixing lots OpenJDK compatibility bugs.<p>Android still needs to run dex bytecode <i>somehow</i>, so there are two possibilities for how N will work.<p>Option one is that Android stick with ART and replaces Harmony with OpenJDK: from a technical perspective, that wouldn't be the end of the world, especially since the Harmony implementation is rather inefficient.<p>Option two is that Google ports Hotspot to run on Android and, then has PackageManager convert dex bytecode <i>back</i> to Java bytecode on device. That would be awful, since ART is built for low-end devices and, well, Hotspot isn't.<p>In favor of option one is that Google is still developing ART. In favor of option two is Oracle being Satan incarnate.<p>I also wouldn't be surprised if Oracle has compelled Google to simply <i>ship</i> a copy of Hotspot, allowing developers to ship "authentic Java" APKs instead of dex-bytecode ones, with the two environments running in parallel, with two different zygotes.