Software bloat
Software bloat describes the tendency of software to become unnecessarily large, slow, or complex over time, relative to the value it delivers to users. It manifests as excessive memory and CPU consumption, slow startup and response times, large installation footprints, and user interfaces cluttered with rarely-used features.
The phenomenon is observed in many categories of major user-facing software product, including word processors, web browsers, and operating systems.
The phenomenon is closely associated with scope creep. As software matures and successive teams add features to satisfy an ever-broader set of use cases, the product accumulates weight without a corresponding increase in usefulness for any individual user.
The same dynamic is amplified in shrinkwrap software, where the vendor’s revenue depends on persuading existing customers to buy each new version. Each release therefore carries a commercial incentive to add features, regardless of whether users asked for them.
Dependency bloat is a related concern in modern software, where applications transitively pull in far more third-party library code than they actively use.
Niklaus Wirth observed the broader pattern as early as 1995, in what became known as Wirth’s Law, that software grows slower faster than hardware grows faster, meaning that gains in hardware performance are routinely absorbed by the increasing demands of new software, rather than producing a faster user experience.
A parallel corollary holds that data expands to fill the storage available for it, the same dynamic that Parkinson’s law states for time. Larger disks and cheaper memory invite larger formats, logs, caches, and retained histories, rather than leaner ones.
Bloat can also originate from legitimate technical constraints, such as the need to maintain backwards compatibility, to support a wide range of platforms and configurations, and to preserve deprecated code paths. These requirements all add bulk without adding visible value.
Countermeasures include deliberate feature pruning, enforcing architectural modularity and enabling users to choose to include only the components they need, and establishing clear deprecation policies that allow legacy code to be removed rather than retained indefinitely.