With Google's move to integrate OpenJDK in Android, Oracle gains influence over a significant part of the Android software stack
Andreas Gal : Tweets: @fmnjohn , @pquerna , @fraserspeirs , @stshank and @luisobo Tweets: John Carroll / @fmnjohn : Google really missed a trick when it opted not to buy Sun. Could have kept Java and jettisoned everything else. http://twitter.com/... Paul Querna / @pquerna : Oracle sinks its claws into Android http://andreasgal.com/... by @andreasgal “OpenJDK is about as open as a prison” Fraser Speirs / @fraserspeirs : Some deep OSS background here but bottom line: instability ahead for Android. http://andreasgal.com/... Stephen Shankland / @stshank : Google's Android shift to OpenJDK is a huge win for @Oracle, says @andreasgal. “Oracle is a mobile titan now.” http://andreasgal.com/... Luis Solano / @luisobo : This why Apple wants to control everything, including programming languages http://andreasgal.com/...
Context & Ripple Effects
Google had already confirmed that the next Android version would stop implementing Oracle's proprietary Java APIs (the December confirmation) — and this OpenJDK integration is the concrete mechanism behind that shift. Andreas Gal's argument is that swapping in the OpenJDK codebase doesn't free Android from Oracle: it hands Oracle governance over a core layer of the stack.
The move lands mid-fight. Oracle is pursuing up to $9.3B in damages for Android's use of Java (court filings show), with Schmidt, Schwartz and Rubin testifying at the outset of the second trial (the May hearing) and Safra Catz framing Android as having split the Java community. Rebuilding Android on Oracle-governed OpenJDK changes both the technical and the legal terrain of that dispute.
First-order effects
- Oracle gains de facto influence over a significant part of the Android software stack, because the OpenJDK codebase Android now tracks is governed by Oracle rather than by Google's clean-room Harmony implementation.
- Google immediately reduces its legal exposure on the API-copying question: aligning with OpenJDK removes the divergence between Android and the Java reference implementation that Oracle's damages case rests on.
Second-order effects
- Oracle's litigation strategy has to absorb the shift — its claim that Android harmed the separate Java SE market gets harder to sustain when Android runs the open implementation, which is why Oracle pressed new-trial arguments like undisclosed Chrome OS app support later in the year.
- OEMs and Android developers face the instability Fraser Speirs and other commentators flagged: the runtime under their apps is being swapped out mid-release cycle, making upstream OpenJDK release cadence an external dependency for every Android ship.
Third-order effects
- If the pattern holds, control of a platform's foundational layer migrates from who wrote the original API to who governs the open-source reference implementation — a structural lesson for any ecosystem built on someone else's language runtime.
- The episode sets up a longer question about whether open-source licensing can defuse copyright-based API disputes at platform scale, or whether it merely relocates the chokepoint to the steward of the codebase.
The trend: Mobile platform disputes are shifting from fights over proprietary API copying to contests over who governs the open-source implementations platforms depend on.