Could we build a computer designed to last at least fifty years? (2021)

Original Article ↗ Hacker News Discussion ↗

Existing Long-Lived Systems

  • Many commenters note working 30–40+ year old machines (C64, Apple II/IIGS, TRS-80, Amiga 3000, early Toshibas, naval fire-control computers, school-heating controllers).
  • Space and defense systems (Voyager probes, missile silos, telecom switches, nuclear‑related systems) are cited as de facto “decades‑long” computers.
  • Relay and mainframe systems in industry and transit are still in active use after many decades.

Hardware Reliability and Failure Modes

  • Old hardware often fails at capacitors, bearings, transformers, hard drives; these are usually replaceable.
  • Older, larger‑node silicon and leaded solder are seen as more durable; smaller modern processes are said to wear out faster and be more fragile (whiskers, atom migration).
  • Some argue that with careful component choices (no electrolytics, no BGAs, robust PCB materials, good encapsulation) boards could last centuries, leaving PSU and storage as main weak points.
  • Others reference aerospace data showing complex, subtle failure modes that make a truly untouched 50‑year system unrealistic without scheduled part replacement and redundancy.

Software, Internet, and Security Obsolescence

  • Hardware can keep running, but browsers, TLS versions, media formats, and bloated web apps make old machines effectively unusable online.
  • Security updates, microcode flaws, and OS end‑of‑support are major retirement drivers, especially for internet‑connected systems.
  • For offline word processing, coding, or retro tasks, many decades‑old systems remain sufficient.

Design Priorities: Modularity, Repairability, and Use Case

  • A “50‑year computer” is seen as requiring modularity, standard interfaces, and easy part replacement; more like mainframes or desktops than sealed consumer gadgets.
  • Some envision offline‑first machines that sync in deliberate batches, reducing update pressure and attack surface.
  • Others stress that longevity must be scoped: “last 50 years doing what?”—fixed tasks vs general‑purpose, evolving workloads.

Economics, Markets, and Policy Incentives

  • Consumer laptops and phones are often described as flimsy and disposable, contrasted with durable business‑grade hardware.
  • Proposals include recycling/disposal fees (upfront or at end‑of‑life) to incentivize longer lifespans and repairability; real implementations in some countries are mentioned but seen as weak levers.
  • Market demand for thin, light, powerful, waterproof devices is viewed as a core barrier to repairable, long‑life designs.

Phones, Batteries, and Ruggedization

  • Non‑replaceable batteries and fragile screens are criticized as deliberate barriers to longevity; others cite waterproofing, size, and complexity as genuine trade‑offs.
  • Rugged phones with swappable batteries and seals exist but are niche, bulkier, and often mid‑range; commenters disagree whether the bottleneck is demand or manufacturer priorities.

Role of Open Source and Backward Compatibility

  • Long‑lived software ecosystems are credited to backward‑compatible architectures (IBM mainframes, x86, DOS) and emulation.
  • Debate over whether open source is strictly necessary: some argue archived proprietary binaries can be “frozen in amber”; others say open source is essential for porting to new hardware over decades.

Perception of Slowing Obsolescence

  • Several note an “end of history” feeling: 8–10‑year‑old laptops and phones remain usable, unlike earlier eras where 10‑year gaps meant total obsolescence.
  • Performance gains now matter less than durability and software support for many everyday tasks.