Google's Tim Lindholm faces off with David Boies on Java license
David Boies, Oracle's lead lawyer in the Silicon Valley trial of titans, had a nice set-up for day four of the proceedings. On day three, Wednesday, Boies probed Google CEO Larry Page about his familiarity with Tim Lindholm …
Context & Ripple Effects
The Oracle-Google fight has been building for eighteen months before this courtroom moment: Oracle sued over Android's Java use in 2010, Google moved to have the case thrown out that October (Google asked the court to toss Oracle's Android lawsuit), and through 2011 the parties fought hardest not over code but over a single contested Lindholm draft email that both sides treated as potentially decisive.
With the trial underway this week in San Francisco, the witness list has escalated fast — Larry Page spent time on the stand on Tuesday (Page testified in the Oracle trial) — and now Oracle's lead counsel David Boies turns to Tim Lindholm himself, the engineer at the center of the Java licensing question. Putting Boies face-to-face with Lindholm signals Oracle believes the license-negotiation record, not technical infringement arguments, is where the case will be won.
First-order effects
- Lindholm's cross-examination puts his knowledge of Sun's Java licensing terms directly in front of Judge Alsup's court, making what Google knew about needing a license the live evidentiary battleground rather than whether the APIs match technically.
Second-order effects
- A finding that Google knowingly proceeded without a Java license raises the damages calculus for Android's handset partners, whose devices are the distribution vehicle for whatever liability attaches to the platform.
Third-order effects
- If the pattern holds, reimplementing another vendor's API without a license becomes a litigable risk across the industry, pushing platform owners toward explicit compatibility licensing instead of de facto open interfaces.
The trend: Mobile-platform competition is being settled less in product markets than in courtrooms over foundational software interfaces, with API ownership emerging as the industry's next major legal fault line.