liveBook · Manning

Obsolescence

As explained in The Art of Code

Technological obsolescence is the condition in which functioning hardware becomes unusable because its supporting software is unavailable or its capabilities are insufficient for current software.

Technological obsolescence occurs when functioning hardware becomes unusable because its supporting software is no longer available or newer software exceeds its capabilities. The device may remain physically sound while software support, processing power, or memory leaves it behind. section 8.2.2 section 8.6

A working device that cannot be used

A digital photo frame can stop working when its manufacturer shuts down the required cloud service. A child’s tablet can remain in good condition but lose access to new apps because its operating system is no longer updated. Rapidly expanding web pages, with larger images, libraries, and background scripts, can similarly push older hardware beyond its practical limits. section 8.2.2 section 8.2.2

Obsolescence matters because:

  • Replacing usable hardware creates additional environmental debt when most of its carbon impact has already been produced during manufacturing. section 8.2.2
  • Longer use, repair, reuse, and repurposing help amortize embodied carbon over a device’s lifespan. section 8.2.2
  • Efficient software can reduce pressure on older devices through frugal features, lean dependencies, efficient execution, and controlled memory use. section 8.6

How The Art of Code covers it

How deep it goes
Defines two causes and illustrates them with device and web examples, without descending into implementation details.
Examples
Uses a cloud-dependent photo frame, an unsupported tablet, increasingly heavy web pages, and the Apollo-era computer as examples.
What you can do after
Evaluate how software support and resource demands can shorten hardware lifespans and increase replacement pressure.
How it connects
Links technological obsolescence to embodied carbon footprint, software efficiency, and green design patterns.

This explainer was generated by Manning's knowledge graph from the text of The Art of Code. The section links point to the parts of the book it draws on.