TECHNICAL MEMORANDUMTM-26-008
SUMMARY. In 1996 Marcus Meißner and I wrote a terminal emulator in Java so that a text-only multiplayer game could be played from a browser. The applet is long dead. The emulator is not: its terminal code is part of the remote management built into Oracle server hardware, and Oracle's licensing manual lists my name. Nobody planned this. That is the finding.
1. BACKGROUND. TM-26-007 described the text-only multiplayer game whose foundation code I wrote as a student. Java arrived in 1995 with applets in tow, and the obvious next step was the game in a browser page instead of a telnet window. Marcus Meißner and I wrote JTA, a full VT320 terminal emulator with a telnet stack, packaged as a Java applet, and announced it on Usenet in March 1996. The package namespace still records where it came from: de.mud. Telnet came first; SSH support followed when the world moved on.
2. FINDINGS.
2.1 The platform died; the library did not. Applets are gone, but JTA had long become an embeddable library by the time they went. The surviving history counts 528 commits from 1999 to 2017, with copyright lines starting 1996 - two decades of maintenance for a hobby project.
2.2 A terminal emulator implements a fossil standard. JTA emulates the full VT320, written against the original hardware: I owned one at the time, and the real terminal was the reference. The escape sequences trace back to the VT100 of 1978 and do not change. Code that implements a boring standard completely does not age the way application code ages: at some point it is simply done. Done is rare, and done gets reused.
2.3 The paperwork was four emails, thank-you note included, and took less than an hour. JTA was public under the GPL. ILOM, the lights-out management processor in Sun's - later Oracle's - servers, needed the one thing a game client from 1996 could offer: a terminal emulator for its remote console. In November 2008 someone at Sun asked for the de/mud/terminal package under the LGPL 2.1. My side of the negotiation was one sentence. The Oracle ILOM Licensing Information User Manual quotes that email to this day, name and all.
3. CONCLUSIONS. An enterprise afterlife cannot be planned, but it can be made possible: implement a standard that does not move, implement it completely, and keep the licensing simple enough that the whole deal fits in one email. The code in TM-26-007 survived by staying in one place for thirty years. This code survived by traveling into hardware I have never touched. Same discipline, opposite ends: systems that outlive their builders.
4. ACTION. None required. The repository still serves from my own git server, and the last commit is from 2017. The code stopped needing its authors a long time ago - by the standard of TM-26-007, that means it is doing fine.