Write Once, Run Forever: Java's Odyssey

Last weekend, I saw Christopher Nolan's The Odyssey. Great movie. It has gods, monsters, storms at sea, an impossible journey, and a runtime that, to be honest, had us praying for landfall.

A few days later, I watched Write Once, Run Forever: The Java Story, which premiered free on OpenJDK's YouTube channel on July 17. One of these films was shot with IMAX cameras and cost a few hundred million dollars to make. The other weaves together clips of engineers talking, intercut with grainy, archival news footage and conference presentations about a programming language.

And yet, the more I watched the Java movie, the less it felt like a documentary about a programming language, and more like a story of survival.

Watch closely, and another story begins to emerge. A promising young hero sets out with one destination in mind, is blown wildly off course, survives rivals, monsters, betrayals, and his own missteps, and eventually returns not to the place he/she left, but to something better.

Homer gave Odysseus ten years to get home. Java took thirty. To be fair to Java, Homer never had to deal with Microsoft. Odysseus survived a war, a cyclops, a witch who turned his crew into pigs, the wrath of Poseidon, and a house full of opportunists waiting to divide his kingdom. Java had to survive Redmond, the dot-com crash, years of stagnation, and an industry that declared it dead every few years with almost ritualistic enthusiasm.

The Departure
Every epic journey begins with a destination that turns out to be the wrong one.

Java wasn't built for the Web. It wasn't even built for personal computers. The Green Project was chasing interactive consumer electronics and set-top boxes long before anyone imagined the internet becoming the world's software platform. The project failed badly enough that its engineers were laid off, only to be pulled back together when their bosses realized the Web needed exactly the technology they had already built.

That may be the documentary's first lesson. The technologies that change the world rarely begin by trying to.

The Sirens
Then came success. Not ordinary success, but the kind that arrives so quickly it threatens to overwhelm the people responsible for it.

The documentary lovingly revisits the fever dream that was 1995: the spinning Coca-Cola can, Duke doing somersaults inside a browser, newspaper headlines before Java 1.0 had even shipped, engineers discovering the JVM specification for sale in a Vatican City bookstore.

One interviewee recalls smuggling an unauthorized high-speed internet connection into Sun because the company's own network couldn't handle the demand. It's a wonderful story because it captures both exhilaration and hubris. The engineers got everything they wanted. They just weren't prepared for what that actually meant.

Scylla and Charybdis
Every long journey eventually narrows into a passage where danger waits on both sides. In this movie, Microsoft was the first monster. The film makes a compelling case that Redmond's attempt to fragment Java into a Windows-specific implementation threatened something much larger than a programming language. "write once, run anywhere" only worked if everyone played by the same rules. Compatibility wasn't a feature. It was the entire idea.

The lawsuit that followed dominates much of Java's middle years, complete with internal Microsoft emails presented in the film almost like recovered battlefield dispatches. It's easy to forget how existential that fight felt.

Then came the second monster: the dot-com collapse, which devastated Sun and dragged Java into years of uncertainty. The platform that had for a while seemed unstoppable suddenly looked stranded alongside the company that created it. Several interviewees describe the period with remarkable candor. Innovation slowed. Competing languages surged ahead. "Java is dead" became one of the technology industry's favorite recurring headlines.

Odysseus lost crew members. You could argue that Java lost nearly a decade.

The Suitors
Meanwhile, the kingdom didn't stand still. C#, newer programming languages, and restless developers all began circling what looked like an aging platform. One of the documentary's pleasures is watching former critics retrace their steps. Java 8, with lambda expressions and streams, convinced even some of the language's loudest skeptics that the old king wasn't finished after all.

The conversion isn't portrayed as marketing. It's portrayed as engineering. Lambda expressions, streams, and a renewed commitment to evolving the language convinced even some of Java's loudest skeptics that the old king wasn't finished after all.

The Homecoming
The documentary's biggest surprise isn't Microsoft's role. It's Oracle's.

Among developers, Oracle is often remembered as the company that acquired Sun. Write Once, Run Forever argues for something more nuanced. Oracle inherited a platform whose future was genuinely uncertain, then gave it disciplined stewardship, predictable releases, and the confidence to modernize without abandoning its core promise.

Java 8. Lambdas. The six-month release cadence. Project Loom. Project Panama. Project Valhalla. The film doesn't argue that Oracle reinvented Java. It argues that Oracle gave Java the stability it needed to reinvent itself.

That's an important distinction, because Java's homecoming isn't a return to Sun Microsystems. Sun never made it home. Java did.

The Journey's Blind Spots
No odyssey can include every adventure, and this one leaves a few islands unexplored.

The Oracle v. Google litigation, arguably the defining legal battle of Java's adulthood, receives only one perspective and reaches its conclusion rather quickly for a case that reshaped the software industry's understanding of APIs and copyright. Viewers unfamiliar with that history may come away thinking the story was simpler than it really was.

The film also loses a bit of dramatic momentum once the existential threats are behind it. Governance, standards bodies, release cadences, and stewardship are essential to understanding why Java is still thriving today, but they don't carry the same cinematic weight as the battles that came before them.

Then again, perhaps that's the point. Heroic journeys eventually give way to quieter work. Once the monsters are gone, someone still has to keep the kingdom running.

The Verdict
Still, it's difficult to shake the larger story once you've seen it. This isn't really a documentary about Java. It's a film about stewardship.

Every few years our industry becomes convinced that the next language, framework, or AI model will replace everything that came before it. Java tells a different story. Great technologies don't survive because they refuse to change. They survive because they evolve without abandoning the principles that made them valuable in the first place.

That's why Java is still here. Not because it won every battle or that every decision was the right one. Java endured because generation after generation of engineers treated it less like a product and more like a responsibility. They modernized it without breaking it. They challenged it without abandoning it. They understood that compatibility wasn't technical debt. It was a promise.

That's a lesson worth remembering, whether you're writing Java, Rust, Python, or prompting an AI model.

The documentary ends with James Gosling reflecting that the most interesting developments are the ones nobody can predict. Thirty years after Java set out for a destination that didn't yet exist, that observation feels exactly right.

Odysseus returned to Ithaca. Java returned to its purpose: helping ordinary programmers solve real problems. That's a much harder journey.

And a much better story.

Posted by John K. Waters on July 23, 2026