3 ms·
1) software grows and evolves in complexity over time while hardware remains constant until it is upgraded, this explains the macro or low frequency component o
by a-dub 3y ago
1) software grows and evolves in complexity over time while hardware remains constant until it is upgraded, this explains the macro or low frequency component of the slowdowns (ie, things that reinstalling the o/s won't totally solve)
2) local state grows and evolves in complexity. configuration databases grow, new files are added to the filesystem, software upgrades leave unused state around (because getting software upgrades right is still a not-totally-solved problem), indexes (or similar) of mutable state grow but sometimes don't get rebuilt causing locality to suffer affecting cache performance.
3) psychology.
- sys_64738 3y ago> software grows and evolves in complexity over time AKA software bloat. The amount of layers of garbage in an OS today is horrendous.
- kstrauser 3y agoI don’t miss each program coming with its own set of printer drivers. Or only having one type of storage: a directly attached disk of one of a few specifically supported models. Or each program having to decode images in its own code. Or having to POKE specific memory addresses to put a dot on the screen. Each of those layers provide baseline functionality that lots of programs can use. Most of the time, “bloat” is another way to say “the features I don’t use”. Yes, sometimes people push bad code to production. Other times it’s new inherently more complex code that makes computers nicer to use.
- Gigachad 3y agoWhich layers do you think are not useful?