Starting in 2021, a Java programmer who compiled code that touched applets got a line of text she hadn't asked for: the feature "has been deprecated and marked for removal." Applets were small Java programs that ran inside web pages, the 1990s promise of software delivered through a browser. The warning came from the compiler, the tool that turns source code into a working program, so it reached people only while they were looking at their code and could still change it.
By then the browsers were already gone. Chrome dropped the plug-in system applets relied on in 2015, Firefox followed in 2017, and in 2018 Oracle left its Java plug-in out of new Java releases, starting with Java 11. Oracle deleted the applet code from Java 26 this March. Phil Race of Oracle's Java team wrote in a farewell account that the preparatory work had begun in 2016, "so it will have been a 10 year project." A decade to remove something the browsers had already abandoned can look like drift, but in Race's account much of the work went into finding what had been built on applets for reasons that had nothing to do with browsers.
There was plenty to find. Thousands of Java's own automated tests used applet code as a convenient frame to run inside. The official specifications still mentioned applets in passing. Some desktop programs used an applet as an ordinary panel in a window. And some developers had borrowed AudioClip, a tool for playing sounds in applets, to make ordinary programs beep. Java needed a substitute before it could delete that tool, so a new one, SoundClip, arrived in Java 25, one release early.
The beep case is worth pausing on, because the developers behind it made a reasonable choice. A programmer needed a sound, found a player that worked, and used it. That kind of reuse is how software gets built quickly. The cost shows up later, usually for a different team, years on, which has to retire the borrowed part.
Within its own code, Oracle could do that work directly: find each use, write a substitute, then cut. For everyone else's code it relied on the warning. Applets carried the removal label for nearly five years; Stuart Marks, who designed the labeling system, told Java's standards body that about one year is typical.
Five years is generous, but the notice travels mainly through the compiler, plus a scanning tool someone has to think to run. A program built in 2014 and running quietly on a company server never gets compiled again, so it never sees the warning. Oracle's documentation says as much: programs that are never recompiled get no warning and may fail once the code beneath them is gone. The warning reached the people still actively working on their code, who were the least likely to be caught out.
Deleting applets from Java 26 also switched nothing off. An internal tool on Java 8, a 2014 release that companies can still install and that still supports applets, works as it always did. That spares organizations a forced shutdown, but it moves the discovery somewhere Oracle cannot see. The last applet dependencies will surface one company at a time, when an old program moved to a newer Java fails to start and an engineer has to work out why a desktop tool depends on a technology most people remember as a browser feature.
Oracle searched carefully everywhere its own maintainers could look. The rest of the search has been handed out in pieces, across years of separate upgrades at separate companies, each small enough that it is unlikely to be counted as part of the applet's retirement.

