Wirth's Law
Updated 2026-08-05
INTRODUCTION
English translation pending.
CORE DEFINITION
Attributed to Niklaus Wirth, the observation states that software grows slower and heavier faster than hardware improves, so user experience often fails to benefit from faster machines. The mechanism is that developers rely on hardware headroom rather than optimizing, and each layer of abstraction and dependency adds overhead. The core claim is that performance must be actively defended rather than assumed. The qualification is that the trade-off is often deliberate, since development speed and features may matter more than runtime efficiency.
SCAFFOLDING EFFECT
Reduce cognitive load
- Use Performance Budget: Set an explicit ceiling on size, memory, or latency before adding features. - Use Subtraction Audit: Regularly remove unused features and dependencies rather than only adding. - Use Bloat Suspicion: Treat the assumption that faster hardware will fix slowness as a warning sign.
Anchor fast decisions
When hardware capacity is expected to grow, the pressure to optimize code falls, so developers trade efficiency for convenience through abstractions and dependencies. Each layer adds overhead, and the accumulated weight grows at least as fast as the hardware improves. Because the cost is paid by users rather than by the developers who incur it, the drift continues unless a deliberate budget constrains it.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Wirth's_lawverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS