Profile of Judge William H. Alsup of Oracle v. Google and Waymo v. Uber, who ruled against API copyright and taught himself to program in QuickBASIC
On May 18th, 2012, attorneys for Oracle and Google were battling over nine lines of code in a hearing before Judge William H. Alsup of the northern district of California.
Context & Ripple Effects
This profile lands mid-arc in a decade-long fight: Judge William H. Alsup had already ruled that APIs are not copyrightable in Oracle v. Google, and weeks before this piece a jury unanimously found Google's use of Java APIs in Android was fair use — with Oracle vowing to appeal. The profile explains why that technical call came from this particular judge: he taught himself QuickBASIC to understand the nine lines of code at issue in the May 2012 hearing.
What makes the profile durable is that the dispute didn't end here. Oracle's appeal pushed the question of whether APIs are copyrightable all the way to the Supreme Court, which ultimately sided with Google 6-2 and overturned Oracle's win in the 2021 ruling. Alsup also presided over Waymo v. Uber, making him one of the few judges sitting atop both of Silicon Valley's defining litigation fronts.
First-order effects
- Alsup's non-copyrightable-APIs ruling directly enabled the jury's fair-use verdict for Google, forcing Oracle onto an appellate track rather than letting it collect damages from Android's use of Java APIs.
- Google's Android business kept its Java API implementation intact through the trial phase, while Oracle absorbed the cost of a multi-year suit hinging on a judge who could read the code himself.
Second-order effects
- Oracle's vow to appeal after the fair-use verdict escalated a district-court dispute into a Supreme Court test case, dragging other companies whose products depend on reimplemented interfaces into the blast radius.
- The FOSS-philosophy gap Motherboard flagged among judges and jurors became a live concern for every litigant: outcomes turned on how much technical grounding the bench brought to questions like what an API declaration actually is.
Third-order effects
- If the pattern holds, software copyright disputes get decided by how courts treat interfaces — and the Supreme Court's eventual 6-2 Google win cemented Alsup's instinct that declaring an API is not owning it, setting the boundary for interoperable software industry-wide.
- Judges who invest in technical literacy, as Alsup did teaching himself to program, become a structural variable in tech litigation: the same skill shaped both Oracle v. Google and his handling of Waymo v. Uber.
The trend: Software copyright law is being settled top-down — from a technically fluent district judge's API ruling through appeals to a Supreme Court verdict — with interface copyrightability now the precedent every platform dispute inherits.