Museum Wire
Law 0 · Katie's LawEvery system is shaped by the human drive to do less work. This is not a flaw. It is the economic force that produces all software — and all software failure.◆Law I · Boundary CollapseWhen data crosses into a system that interprets structure, without being constrained, it becomes executable.◆◆ 2026 IncidentAxios. 70 Million Downloads a Week. North Korea Inside.◆Law II · Ambient AuthorityWhen a system trusts the presence of a credential instead of verifying the intent behind it, authentication becomes indistinguishable from authorization.◆◈ AXM-001Set Theory — Membership, Boundaries, and Belonging◆Law III · Transitive TrustWhen a system inherits trust from a source it did not verify, the attack surface extends to everything that source touches.◆◆ 2026 IncidentClaude Code — The Accept-Data-Loss Flag◆Law IV · Complexity AccretionSystems do not become complex. They accumulate complexity — one reasonable decision at a time — until no single person can hold the whole in their head.◆Law V · Temporal CouplingCode that assumes sequential execution, stable state, or consistent timing will fail the moment concurrency, scale, or latency proves the assumption wrong.◆◆ 2026 IncidentCopy Fail — 732 Bytes to Root on Every Linux Distribution◆◈ AXM-002Boolean & Propositional Logic — True, False, and the Excluded Middle◆Law VI · Observer InterferenceWhen the system that monitors health becomes a participant in the system it monitors, observation becomes a failure vector.◆◆ 2025Amazon Kiro — The 13-Hour Outage◆◆ 2025Operation Chrysalis: The Notepad++ Supply Chain Hijack◆◆ 2025Replit Agent — The Vibe Code Wipe◆◆ 2025Shai-Hulud — The npm Worm That Ate Its Own Ecosystem◆◆ 2024Air Canada Chatbot — The Policy That Wasn't◆◆ 2024Change Healthcare — One-Third of US Healthcare, One Missing MFA◆◆ 2024CrowdStrike — The Security Update That Broke the World◆◆ 2024Google Gemini Image Generation — The Six-Day Pause◆◆ 2024XZ Utils — The Two-Year Infiltration◆◆ 20233CX — The Supply Chain That Ate Another Supply Chain◆◆ 2023Amazon Prime Video — The Per-Frame State Machine◆◆ 2023Bing Sydney — The Chatbot That Went Rogue◆◆ 2023Samsung ChatGPT Leak — The Employee Who Pasted the Secret◆EFFODE · LEGE · INTELLEGE◆Law 0 · Katie's LawEvery system is shaped by the human drive to do less work. This is not a flaw. It is the economic force that produces all software — and all software failure.◆Law I · Boundary CollapseWhen data crosses into a system that interprets structure, without being constrained, it becomes executable.◆◆ 2026 IncidentAxios. 70 Million Downloads a Week. North Korea Inside.◆Law II · Ambient AuthorityWhen a system trusts the presence of a credential instead of verifying the intent behind it, authentication becomes indistinguishable from authorization.◆◈ AXM-001Set Theory — Membership, Boundaries, and Belonging◆Law III · Transitive TrustWhen a system inherits trust from a source it did not verify, the attack surface extends to everything that source touches.◆◆ 2026 IncidentClaude Code — The Accept-Data-Loss Flag◆Law IV · Complexity AccretionSystems do not become complex. They accumulate complexity — one reasonable decision at a time — until no single person can hold the whole in their head.◆Law V · Temporal CouplingCode that assumes sequential execution, stable state, or consistent timing will fail the moment concurrency, scale, or latency proves the assumption wrong.◆◆ 2026 IncidentCopy Fail — 732 Bytes to Root on Every Linux Distribution◆◈ AXM-002Boolean & Propositional Logic — True, False, and the Excluded Middle◆Law VI · Observer InterferenceWhen the system that monitors health becomes a participant in the system it monitors, observation becomes a failure vector.◆◆ 2025Amazon Kiro — The 13-Hour Outage◆◆ 2025Operation Chrysalis: The Notepad++ Supply Chain Hijack◆◆ 2025Replit Agent — The Vibe Code Wipe◆◆ 2025Shai-Hulud — The npm Worm That Ate Its Own Ecosystem◆◆ 2024Air Canada Chatbot — The Policy That Wasn't◆◆ 2024Change Healthcare — One-Third of US Healthcare, One Missing MFA◆◆ 2024CrowdStrike — The Security Update That Broke the World◆◆ 2024Google Gemini Image Generation — The Six-Day Pause◆◆ 2024XZ Utils — The Two-Year Infiltration◆◆ 20233CX — The Supply Chain That Ate Another Supply Chain◆◆ 2023Amazon Prime Video — The Per-Frame State Machine◆◆ 2023Bing Sydney — The Chatbot That Went Rogue◆◆ 2023Samsung ChatGPT Leak — The Employee Who Pasted the Secret◆EFFODE · LEGE · INTELLEGE◆
Keyboard Navigation
W↑
A←
S↓
D→
or arrow keys · M for map · Q to exit
← Back to Hall of Heroes
Commodore 64 pixel portrait
⬡ Pioneer◉ Voiceboth

Commodore 64

C64

The Best-Selling Computer of All Time, Killed by Its Creator

eighties · 3 min read · Decommissioned
“Computers for the masses, not the classes.”

The Machine

The Commodore 64 launched in August 1982 at $595. Within a year, price competition had brought it below $200. The SID (Sound Interface Device) chip produced three-voice synthesis with independent volume, waveform, and filter control that had no equivalent in the home computer market. The VIC-II graphics chip provided hardware sprites — independently moving objects the CPU didn't need to manage — at a time when Apple II and TRS-80 were drawing everything in software.

Developers discovered you could push the hardware beyond its specifications. DMA tricks, raster interrupts, timing exploits — the C64 demoscene that emerged from these techniques is still active today, forty years later. The machine inspired a form of programming that is closer to the machine as a musical instrument than the machine as a tool.

The Disk Drive

The Commodore 1541 disk drive — the C64's standard storage device — had its own 6502 processor and ran at 300 baud over a serial bus that Commodore had deliberately slowed because the VIC-20 couldn't run the IEEE-488 bus fast enough and they used the same bus for the C64. The disk drive was as powerful as an Apple II and ran at 1/10th the speed it was capable of. Loading a program took minutes. The third-party fast-loader cartridge industry existed entirely because Commodore shipped a crippled serial protocol.

This is an exhibit: an engineering decision made for one product (VIC-20 cost reduction) that became a permanent constraint on a successor product (C64), enforced by hardware compatibility, never fixed in 12 years of production.

The Killing

Commodore International went bankrupt in April 1994. The C64 was still in production. The Amiga — technically superior to both the Mac and the PC for multimedia — had been on the market for nine years and still hadn't been properly marketed. Commodore's engineering teams built machines that were five years ahead of the market. Commodore's management teams failed to market, price, or distribute them.

The C64's death is Complexity Accretion at the corporate layer: each product decision — ignore the Amiga, underprice the C64, cede the business market to IBM, fight price wars instead of building infrastructure — was made independently. The aggregate was the destruction of the most successful home computer company in history.

The best-selling computer in history was killed by the company that made it. The machine outlasted the company. The SID chip inspired musicians for forty years. Commodore's management is documented here as a warning.