3 ms·
> They implemented their own runtime environment that's mostly API compatible with Java (and getting further from that as the years go on). That's not quite ri
by sangnoir 9y ago
> They implemented their own runtime environment that's mostly API compatible with Java (and getting further from that as the years go on).
That's not quite right - Google adopted Apache Harmony[1] (an open source project, and if you want to attribute an organisation responsible for Harmony's success - such as it was - it would be IBM). Apache Harmony would have been 100% API compatible with Java had Sun (and later Oracle) not refused to provide the Technology Compatibility Kit (TCK).
The Android runtimes (Dalvik, then ART) never had compatibility with Java bytecode, instead, Android build-tools use(d) Java bytecode as an intermediate pipeline step; the ultimate executable had 0% compatibility with the Java runtime.
- AnimalMuppet 9y agoI don't think that's quite right, either (though I could be wrong). IIRC, Android first was done based on Sun/Oracle Java. Then (and maybe even after the lawsuit started?), Google shifted to Harmony.
- sangnoir 9y agoAre you perhaps referring to Android's very recent switch to GPL-licensed OpenJDK[1] from Harmony after the lawsuit? There was no GPL licensed (and certified) version of Java when the Android project kicked off - OpenJDK came into existance later. Also - Apache Harmony predated OpenJDK by a few years. 1. https://arstechnica.com/tech-policy/2016/01/android-n-switches-to-openjdk-google-tells-oracle-it-is-protected-by-the-gpl/ https://arstechnica.com/tech-policy/2016/01/android-n-switch...
- AnimalMuppet 9y agoYes, that's what I meant.