When Java applets promised to run anywhere (but mostly just asked you to update Java Runtime Environment)
In 1995, Sun Microsystems unveiled Java with a pitch that sounded almost too good to be true: "Write once, run anywhere." The idea was brilliant in its simplicity. Developers could write code once, and it would run on any computer with a Java Runtime Environment installed. No more maintaining separate versions for Windows, Mac, and Unix. No more cross-platform headaches. Just pure, portable software delivered straight through your web browser.
The reality, as anyone who lived through the late nineties and early noughties will tell you, was rather different.
The promise of platform independence
Java applets arrived at a time when the web was still finding its feet. HTML could give you text and images, but if you wanted proper interactivity—games, calculators, data visualisation, anything beyond a hyperlink—you needed something more powerful. Java applets seemed like the answer. They could run inside a web page, work on any operating system, and do things that plain HTML simply couldn't manage.
Banks loved them for secure login systems. Educational sites used them for interactive diagrams. Corporate intranets deployed them for internal tools. For a brief, optimistic moment, it looked like Java applets might become the standard way to deliver rich, interactive content on the web.
That moment didn't last terribly long.
The update treadmill
The first sign that something wasn't quite right usually appeared as a small dialogue box. "A new version of Java is available. Would you like to update now?" Sometimes it would appear before you'd even had your morning coffee. Sometimes it would interrupt something important. Sometimes—and this was the really special bit—it would appear immediately after you'd just updated Java the previous day.
Clicking "update" rarely felt like a quick process. The Java updater would lumber into action, downloading files, checking versions, occasionally deciding it needed to restart your browser or, on particularly ambitious days, your entire computer. And heaven help you if you tried to use your browser while an applet was loading. That little spinning Java icon—that endlessly rotating pinwheel of optimism—would appear, and your browser would essentially down tools until the applet decided it was ready.
Which, depending on the applet's mood and your internet connection, could be anywhere from annoying to "go and make a cup of tea whilst contemplating your life choices" territory.
Security theatre at its finest
Then there were the security warnings. Oh, the security warnings. Every single time you encountered a Java applet, you'd be presented with a stern dialogue box asking if you really, truly, absolutely wanted to run this potentially dangerous code. Did you trust the certificate? Did you understand the risks? Were you certain this wasn't going to do terrible things to your computer?
Most people, faced with this rather alarming interrogation, would click through anyway because they just wanted to view their bank balance or use that interactive chart their colleague had emailed. But it did rather undermine the whole "seamless web experience" thing Sun Microsystems had been hoping for.
The security concerns weren't entirely unfounded, mind you. Java applets ran in a sandbox—a restricted environment designed to prevent them from accessing your files or doing anything too mischievous. But vulnerabilities kept appearing, patches kept being released, and the whole ecosystem developed a reputation for being just a bit risky. IT departments began disabling Java in browsers. Security experts recommended keeping it turned off unless absolutely necessary. The dream of universal, trusted web applications was quietly shelved.
Performance: not exactly snappy
Even when Java applets did work without security warnings or update prompts, they weren't what you'd call responsive. The Java Virtual Machine needed to start up, the applet needed to download, and then—if you were very lucky—something would actually appear on your screen. Watching a Java applet load felt a bit like watching someone try to parallel park a caravan: you knew it would probably work eventually, but you weren't entirely sure how long it was going to take or whether it might give up halfway through.
Simple Flash animations would load and play before a Java applet had even finished thinking about initialising. JavaScript, despite being slower in those days, felt positively zippy by comparison. And native applications? Well, they were in a different league entirely.
The "run anywhere" promise turned into "run everywhere, but not particularly well anywhere."
The slow fade into obsolescence
Java applets lingered far longer than they probably should have. Some corporate systems kept using them well into the 2010s, largely because replacing them required actual work and actual budget. But the writing was on the wall. Browsers started phasing out support. First they required explicit permission, then they deprecated the plugins entirely. Chrome dropped support in 2015. Firefox followed suit. By 2017, Oracle themselves announced that Java applets were essentially finished.
In their place came JavaScript frameworks, HTML5, WebAssembly, and a whole constellation of technologies that actually delivered on the promise of rich, interactive web content without requiring users to maintain a separate runtime environment or nervously click through security warnings.
Java itself survived and thrived—it's still one of the most widely used programming languages in the world. But Java applets? They became a cautionary tale about the gap between ambitious promises and messy reality, a reminder that sometimes the most elegant technical solution isn't the same as the most practical one.
And honestly, we don't really miss that spinning icon.
More trips down memory lane
If you enjoyed this particular slice of technological nostalgia, you'll be pleased to know we've got plenty more where that came from. Our Retro Tech section is stuffed with stories about the technology that shaped the internet we use today—the brilliant ideas, the spectacular failures, and the things that were just a bit odd. These should get you started:
- [Article links will go here]
Why we're fascinated by old tech
We write about retro technology not just for the nostalgic warm fuzzies (though those are admittedly pleasant), but because understanding where we've been helps us build better things today. Every outdated plugin, every abandoned standard, every technology that promised the world and delivered mild inconvenience—they all taught us something. The security problems with Java applets informed how we approach browser security now. The performance issues highlighted the importance of responsive design. Even the update fatigue taught us something about user experience.
The work we do today—the websites we build, the applications we develop, the systems we create—exists because people tried things, learned what worked, and figured out what didn't. Sometimes by making a glorious mess of it first. Here are a few examples of the things we've built, standing on the shoulders of deprecated plugins:
Fancy building something with us yourself?
If you'd like us to build you a website, create some software, or help with a digital project—ideally one that doesn't require users to update their Java Runtime Environment—we'd be delighted to hear from you. We promise to use modern technology that actually works, write code that doesn't trigger security warnings, and deliver something you can use without having to restart your browser. Get in touch and let's talk about what you need.
Why did Java applets always ask me to update?
Java applets required a separate Java Runtime Environment to run, which needed frequent security patches and updates. The updates were so common that users would sometimes see update prompts the day after updating, making it feel like a never-ending cycle.
Are Java applets still used today?
No, they're essentially dead. Chrome dropped support in 2015, Firefox followed, and Oracle officially announced Java applets were finished in 2017. Modern browsers no longer support them at all.
What replaced Java applets for interactive web content?
JavaScript frameworks, HTML5, and WebAssembly took over. These technologies deliver rich, interactive content without requiring a separate runtime environment or triggering constant security warnings.