How US trade politics killed TRON, Japan's bid for a homegrown OS empire

In 1984, University of Tokyo researcher Ken Sakamura launched TRON, a plan to build a single, vertically integrated computing stack spanning everything from washing-machine microcontrollers to desktop workstations to telecom switches. The project spawned five sub-architectures — including the embedded ITRON, the desktop BTRON, and the mainframe CTRON — plus its own CPU (built by Hitachi as the Gmicro/200), keyboard layout, and a character-encoding scheme with a theoretical ceiling of 1.5 million characters that out-covered Unicode’s CJK range for more than a decade and treated Braille as a first-class plane before Unicode encoded it at all. Backed by MITI and a consortium of nearly every major Japanese electronics maker, the specs were open and royalty-free.

BTRON, the desktop variant, was the conceptual standout. Instead of files and applications, its core abstraction was the typed document part — self-describing blocks of content joined by system-managed typed links that survived renames and reorganization, stored in a directed-graph filesystem rather than a directory tree. Applications acted as handlers for part types rather than owners of files. It was, in effect, the block-and-link model that Roam, Logseq, and Obsidian would rediscover decades later, proposed as the fundamental OS primitive in the mid-1980s.

BTRON never got its shot. A 1989 US trade-barrier report named it as an unfair obstacle, and the political pressure effectively killed a planned rollout to Japanese schools before it began. The embedded sibling ITRON, meanwhile, went on to become one of the most widely deployed operating systems ever. The saga later attracted conspiracy theories — including a baseless claim tying the JAL Flight 123 crash to TRON developers — but the more grounded takeaways are that BTRON’s ideas were simply too far ahead of the hardware, and that SoftBank founder Masayoshi Son may have helped undermine it from within.