I advise anyone that actually cares about Java™, to spend some time reading AOSP commits regarding OpenJDK integration.
Before Android N they used to come from Apache Harmony and occasionally classes were borrowed from OpenJDK. But thats no longer the case since Android N.
Many methods don't have a full implementation, some classes have partial implementation and not every library class from OpenJDK is taken into Android.
Thanks to Google now I need to search for Android Java libraries, instead of Java libraries.
Funny every time I search for Java on https://developer.android.com/develop/index.html I get several hundred results, and yet Google doesn't call their fork Java, go figure.
The difference, is that I don't live on Silicon Valley, I don't care about Google nor do I need to keep Android team happy to make a living.
What I care is that now I need to write two libraries instead of one.
Oracle (and Sun before) doesn't have a problem with companies that follow the license rules, there several commercial JDK vendors all of them nicely getting along with Oracle.
Android was never intended to be used for Java portability so nothing has been broken.
>I cannot just take a random Java library and have it work on Android.
Android is not compatible with Java so why would you expect a random Java library, meant to work with Java, to work on Android?
>Thanks to Google now I need to search for Android Java libraries, instead of Java libraries.
A comprehensive list of libraries that work with Android has already been created so why would you need to look for Java libraries?
>Funny every time I search for Java on https://developer.android.com/develop/index.html I get several hundred results, and yet Google doesn't call their fork Java, go figure.
The Android SDK is a fork of the JDK. Did you expect them to rename every instance of the word "Java" to something else just for the sake of differentiation?
>What I care is that now I need to write two libraries instead of one.
I'm sure there are a plenty of libraries that work on either platform, but such is the nature of a fork. Support the platform you care about.
>Oracle (and Sun before) doesn't have a problem with companies that follow the license rules, there several commercial JDK vendors all of them nicely getting along with Oracle.
Google doesn't use the Oracle JDK they use the OpenJDK so why is a commercial license needed to use a forked version of an open source project?
"The successor of Dalvik is Android Runtime (ART), which uses the same bytecode and .dex files (but not .odex files), with the succession aiming at performance improvements transparent to the end users. The new runtime environment was included for the first time in Android 4.4 "KitKat" as a technology preview,[4][5] and replaced Dalvik entirely in later versions; Android 5.0 "Lollipop" is the first version in which ART is the only included runtime."
Bytecode is the thing the Java compiler produces (class files) from your Java source code.
Android N only switched to the Java API (base classes) of OpenJDK. As far as I know they didn't switch runtime environment.
(I know dalvik technically doesn't run bytecode but some other form of intermediary code optimized for mobile devices. I sidestepped that to keep things simple)
One of the greatest accomplishments an adult can achieve.