What the ruling actually decides
The Supreme Court's decision in Google v. Oracle holds that Google's reuse of Oracle's Java API is fair use. Beyond that headline, the opinion treats the ability of developers to carry code and skills from one platform to another as an interest copyright law should protect.
The stakes were concrete: developers spend time learning the platform APIs they build against, and moving a finished program to a different platform costs further effort. Before the Court heard the case, one widely raised concern was that an Oracle win would hand API owners lock-in leverage over developers once a stack had been chosen.
Why APIs sit farther from copyright's core
Fair use analysis weighs how close a protected work lies to the "core" of copyright — how much copyright matters to the work's purpose. The Court placed APIs farther from that core than other code, and developer investment was central to its reasoning:
Unlike many other programs, [an API's] value in significant part derives from the value that those who do not hold copyrights, namely, computer programmers, invest of their own time and effort to learn the API's system. And unlike many other programs, its value lies in its efforts to encourage programmers to learn and to use that system so that they will use (and continue to use) Sun-related implementing programs that Google did not copy.
The market effect and the public interest
Weighing the impact on the overall market, the Court concluded that letting an API owner block reimplementations would work against the public interest, given what programmers have invested, the creativity APIs enable, and copyright's own aims:
Finally, given programmers' investment in learning the Sun Java API, to allow enforcement of Oracle's copyright here would risk harm to the public. Given the costs and difficulties of producing alternative APIs with similar appeal to programmers, allowing enforcement here would make of the Sun Java API's declaring code a lock limiting the future creativity of new programs. Oracle alone would hold the key. The result could well prove highly profitable to Oracle (or other firms holding a copyright in computer interfaces). But those profits could well flow from creative improvements, new applications, and new uses developed by users who have learned to work with that interface. To that extent, the lock would interfere with, not further, copyright's basic creativity objectives.
With the highest Court framing developer interests this way, the decision should support developers' freedom to innovate for years to come.
