Ahead of this month's SCOTUS review of Oracle's 2010 Java copyright infringement case against Google, a look at how Oracle once got rich by copying IBM's SQL
Oracle's history highlights a possible downside to its stance on API copyrights. — More than a decade ago … Tweets: @newsycbot , @markcallaghandb , @grimmelm , and @binarybits Tweets: @newsycbot : Oracle's history highlights a possible downside to its stance on API copyrights https://arstechnica.com/... (cmts https://news.ycombinator.com/ ...) Mark Callaghan / @markcallaghandb : I have been waiting for someone to write about this https://twitter.com/... James Grimmelmann / @grimmelm : In which I argue that is no sharp dividing line between APIs and programming languages for copyright purposes. https://twitter.com/... Timothy B. Lee / @binarybits : Excited to finally publish my deep dive exploring how Oracle was for copying APIs (Oracle copying SQL from IBM) before they was against it (Google copying Java). https://arstechnica.com/...
Context & Ripple Effects
The Oracle-Google dispute has been running for a decade: a jury unanimously found Google's use of Java APIs in Android was fair use in 2016, Oracle appealed, and in 2018 an appeals court revived Oracle's billion-dollar copyright claim, ruling the use wasn't fair use. With the Obama administration having earlier sided with Oracle and damages once pegged around $9.3B (what's at stake), SCOTUS taking the case up this month is the final stop.
This article adds an irony layer to that arc: reporting claims Oracle built its early business by copying IBM's SQL — meaning the company now arguing APIs are copyrightable once profited from exactly the kind of interface re-implementation it wants to outlaw. Commentators like James Grimmelmann seized on it, arguing there is no sharp dividing line between APIs and programming languages for copyright purposes.
First-order effects
- SCOTUS's review directly decides whether Google owes Oracle billions for Android's Java API usage — and whether the 2016 jury verdict survives.
- Oracle's copied-SQL history hands Google's side a ready-made rhetorical and amicus argument: the plaintiff's own success came from re-implementing another firm's interface.
Second-order effects
- If Oracle prevails, every platform that re-implements a competitor's API for compatibility — the pattern Techdirt noted the 2016 verdict protected — faces licensing exposure, shifting bargaining power to whoever owns the original interface spec.
- A ruling for Google would push litigants like Oracle toward contract and patent theories instead, since fair use would remain the shield for re-implementation.
Third-order effects
- The case forces copyright law to draw a boundary Grimmelmann argues doesn't naturally exist between APIs and programming languages — a decision that will define how much of software interop culture survives inside copyright's fence.
- Whichever way it lands, the outcome sets the template for the next generation of interface disputes as more value concentrates in de facto standard APIs owned by a few large vendors.
The trend: A decade of Oracle-Google litigation is driving US copyright law toward its first definitive ruling on whether software interfaces are protectable expression, with interoperability across the industry hanging on the answer.