Java’s early days: cross-platform ABI, applet demos, and the fight against Windows NT

The Stack Overflow Blog has published an interview with Tim Lindholm, an early contributor to the Java language at Sun Microsystems. In the conversation, Lindholm describes the engineering decisions and competitive pressures that shaped Java during its formative years in the mid-1990s. The interview is part of a new documentary by Cult.Repo available on YouTube.

The discussion covers three main areas: the strategic creation of a cross-platform application binary interface (ABI) to compete with Microsoft’s Windows NT, the origins of Java applets as a minor demonstration rather than a core product, and the working culture inside the Sun team that built the language.

Cross-platform ABI as a competitive weapon

Lindholm explains that the Java team deliberately built a cross-platform ABI to give developers a single binary format that could run on any operating system. At the time, Windows NT was gaining enterprise traction, and Sun saw lock-in to a single platform as a threat to its workstation and server business. A portable runtime, Lindholm says, was a direct countermove.

The ABI allowed Java bytecode to execute unchanged across Solaris, Windows, Linux, and later macOS. This technical decision became the foundation of Java’s “write once, run anywhere” promise, which drove adoption in banking, telecommunications, and enterprise IT.

Applets were “just an interesting demo”

Contrary to the popular memory of Java applets as a flagship feature, Lindholm recalls that applets were initially a small, experimental demonstration. The team built a web browser plugin to show that Java could run inside a web page, but the main engineering focus remained on the core language, the virtual machine, and the standard library.

“Applets were never the primary product,” Lindholm states in the interview. “They were a demo that got a lot of attention, but the real work was always the platform underneath.”

The documentary also features other early Sun engineers, though Lindholm is the central figure in the Stack Overflow podcast conversation.

Why this matters for developers today

Java remains one of the most widely used programming languages, powering Android apps, enterprise backends, big data frameworks like Apache Hadoop and Apache Spark, and cloud infrastructure. Understanding the strategic trade-offs made in the early 1990s — especially the bet on a portable runtime over native performance — helps explain why Java’s design still shapes modern languages like Kotlin, Go, and C#.

For developers working with JVM languages, cloud-native Java (Quarkus, Spring Native), or cross-platform toolchains, Lindholm’s account offers a rare look at the original constraints that defined the platform.

Key facts from the interview

What the interview does not cover

The Stack Overflow conversation is relatively short and does not delve into Java’s later controversies, such as the Oracle acquisition, the Google API copyright lawsuit, or the rise of alternative JVM languages. Lindholm also does not discuss Sun’s internal struggles or the eventual decline of the Solaris workstation business. The documentary by Cult.Repo may include additional material, but that content was not available for verification at the time of writing.

Readers who want the full context should watch the Cult.Repo documentary on YouTube and connect with Lindholm on LinkedIn, as noted in the original podcast description.

Source: Stack Overflow Blog — https://stackoverflow.blog/2026/09/01/the-good-ol-days-of-building-java/