TODAY IN NUMBERS
TECHNOLOGY · SATIRE · OUTSOURCED SUBSYSTEM

Apple's Abandoned Operating System Finally Boots in a Browser, and Asks the User to Approve Each of Its Own Objections

Copland's last 1996 developer build now runs on an experimental emulator fork. When it hits an assertion it stops and waits to be told to carry on.

Editorial cartoon illustration: Three colleagues stand behind the chair with folded arms, watching the finger rather than the computer. An unopened cardboard box of old floppy disks sits on the floor beside the table leg.
Editorial illustration by The Questionable Times. Based on the verified event; scene is illustrative.

Copland, the operating system Apple was building to replace System 7 and then abandoned, now boots in a web browser, thirty years after the project was shut down.

It was an ambitious thing for its day: PowerPC-native, built around a microkernel, with protected memory and preemptive multitasking for system services.

Three unfinished developer builds are publicly known, D7E1, D9 and D11E4. The last of them, D11E4, dates from June 1996.

The developer Michael Steil, who goes by Mist, made it run using an experimental fork of the DingusPPC Power Mac emulator. Steil says the 11 patches that enable DingusPPC to boot Copland were written with AI assistance.

What runs is an unstable prerelease, and it behaves like one. If the emulated system hits an assertion, it drops into a debugger and asks the user to continue manually.

Apple acquired NeXT at the end of 1996 and cancelled Copland. The NeXTSTEP-derived Rhapsody followed in 1997, Mac OS X Server 1.0 in 1999 and consumer Mac OS X 10.0 in 2001.

The work was not wasted. Components of Copland were folded into Mac OS 8 in 1997, and into Mac OS 8.1 and Mac OS 8.5 the following year.

As a preservation exercise it is a useful demonstration of how much of a mid-1990s workstation a browser tab can now stand in for.

It is worth being precise about the arrangement, though. Copland was never finished. The part that was least finished was its handling of its own failures. That handling is now performed by a person.

When the system reaches a condition it cannot resolve, it stops and asks. The user says continue. The system continues. Thirty years late, the missing subsystem has been sourced.

Our analysts believe this to be the only operating system whose exception handler has a browser tab. The design is unusually honest: rather than decide what to do about an assertion, it refers the matter upward, to the one component in the stack with no documentation and no release schedule.

On the original specification, protected memory and preemptive multitasking were there to stop one misbehaving program taking the whole machine down with it. The emulated build achieves this by stopping everything and waiting, which is the same outcome reached by consent.

The Department of Unnecessary Research has concluded that Copland shipped, and that the user is part of it.

THE ROAD AWAY FROM COPLANDQUESTIONABLE ANALYTICS
0Copland D11E4, 1996
20Mac OS 8, 1997
60Mac OS X Server, 1999
100Mac OS X 10.0, 2001
Illustrative newsroom graphic, normalised 0-100 across 1996 to 2001. Real dates: Copland's final developer build June 1996, Mac OS 8 in 1997, Mac OS X Server 1.0 in 1999, Mac OS X 10.0 in 2001.
THE BORING FACT

Copland, the operating system Apple was building to replace System 7 and cancelled after acquiring NeXT at the end of 1996, now boots in a web browser via an experimental fork of the DingusPPC Power Mac emulator. If the emulated system hits an assertion, it drops into a debugger and asks the user to continue manually.

Source: The Register
OUR PROFESSIONAL CONCLUSION

Because the emulated build refers each unresolved assertion to the person at the keyboard, the subsystem Copland never finished has been supplied by the user, and the operating system can be recorded as complete.

REALITY CHECK · OUTSOURCED SUBSYSTEM

Unfortunately, there's a small problem.

Dropping into a debugger on a failed assertion is what a prerelease build does: it is evidence the OS was never finished, not a design in which the user is a component. Calling a manual prompt a shipped feature turns a symptom into a specification.

THE BS DETECTOR

Where did reality end?

Tap the paragraph where this story stopped being true. Then see where everyone else bailed.

 

READER CREDULITY METER

Did you believe this story before the twist?

Be the first reader to answer.