Ask HN: Why do computers/tablets/etc "freeze up" as they get older?
Computers, phones and tablets often feel like they “freeze” or slow to a crawl after a few years, largely because newer operating systems, apps and web pages demand more RAM, storage I/O and background services than the original hardware was designed for. Commenters point to factors such as memory thrashing, bloated software, registry and filesystem growth, and cheap or aging flash storage and cooling systems that degrade over time, all of which can create long pauses even if the CPU is still capable. Some also cite battery wear, vendor update policies and developer incentives as reinforcing this pattern, while noting that leaner systems or well-maintained machines can avoid most of these problems.
Software bloat, updates, and changing expectations
- Many argue the main cause is software evolution: OS and apps gain features, daemons, and background services, increasing CPU/RAM and I/O demands on fixed hardware.
- Wirth’s law is cited: software slows faster than hardware improves.
- “Bloat” vs “more capable”: some see added features (rich messaging, cross‑platform UIs, media‑heavy apps) as necessary; others say core productivity hasn’t changed enough to justify the jump in requirements.
- Regular forced updates and mandatory upgrade paths can push newer, heavier software onto old hardware that once ran fine.
Memory, storage, and paging/thrashing
- Excessive paging/swap (“thrashing”) is a recurring explanation: when RAM is insufficient, constant RAM–disk shuffling freezes the UI.
- Full or nearly full disks, slow HDDs, cheap/aging eMMC/flash, poor TRIM/GC behavior, and filesystem/registry bloat are all blamed for long I/O stalls.
- Some recall specific failures: low‑quality flash in tablets, slow SD cards, Windows Update scanning huge local update folders, and snaps’ slow first start.
Hardware aging and thermal issues
- Some point to physical degradation: capacitors drying, flash wear, transistor aging, dust‑clogged fans, dried thermal paste, bad cables, and increased error rates.
- Others counter that most such issues should cause crashes, not gradual slowness, except via mechanisms like thermal throttling or retry logic after errors.
- Batteries degrading can cause voltage drops; on phones this can trigger clock‑speed capping to avoid sudden reboots.
OS, platform, and configuration differences
- Several say they don’t see this “rot” on carefully maintained Linux/FreeBSD systems or on certain Android phones; they attribute problems mainly to Windows, iOS, and cheap Android devices.
- Suggested culprits: accumulating background apps, plugins/extensions, misconfigured caches, phone‑home logic waiting on the network, and IT policies/updates adding bloat.
- Some emphasize user “hygiene” (monitoring resources, cleaning dust, factory resets, avoiding unnecessary plugins) as key to avoiding freezes.
Planned obsolescence, policy, and perception
- Planned obsolescence is mentioned (e.g., non‑upgradeable RAM, OS support cuts, battery‑related throttling), but not everyone agrees it’s primary.
- A few note psychological factors: expectations of speed have risen, making older but unchanged performance feel worse over time.