The traditional path to making a slow operating system is to take a fast one and add features under the 5% rule. If a new feature does not visibly slow the system down or only slows it down 5% or some arbitrary definition of “small”, then it goes in. Each mistake or badly written or poorly architected component then increases the absolute magnitude of that allowable 5% on the next go round. And each introduced performance drag makes it more difficult to improve performance down the line – as it depends on previous mistakes and generates dependencies in future mistakes.
-
Recent
- The UNIX file system as a recursive function
- Apple’s A5 chip made in Austin
- Richard Stallman speaks
- Dennis Ritchie
- Droning on about computer security
- The multics file system
- Fukushima Robot Blog
- Sinking in too many layers
- Computer architecture, power, and PHP
- VCs bailing on signed term sheets
- American corporate management
- Apple’s Patents possibly covering android
- Computer Science 101
- Why computers are more and more devices for generating heat from electricity
- Dutch masters