Given that any software mechanism consist of constant and variable portions (or threaded segments), it can be maintained that the constant portions be written on mask-ROM, and the variable or updatable portions be written an any reliable EEPROM type medium, best of all on Flash chips (Once Called Bubble-Mems, for those who remember), said today as ranging in volumes of Gbytes.
In the ancient days of the eighties, all bootable systems were ready for user input in a matter of milliseconds, right, because the OS was written on Mask-ROM, and from there arranged and projected to RAM, instantly.
Today, The hardware is so reliable, that many of the BIOS routines as part of the Boot "ceremony" are neglible if not obsolete. But Al-In-all, Really, this trivia is known and besides the point.
The Point Is that gradual shift of the software industry from tight and fast "Atomic" development tools such as FORTH, to "structural" OOP App-Generators, such as Visual-Studio.
We've all moved from crafting and optimising Stand-alone "Algo-machines" into an alien kind Assembly, of a collection of "scripts" meant to "orchestrate" system-based object libraries such as API, MFC, and their ever growing family of mutants.
I believe we all know why: for the sake of the all controlling registry and "task-management" systems, which may have originated from MS desire to avoid the free-running of stand-alone apps. The Never really achieved "Multitasking" magical-goal, can be managed at least as poor with of without an all-controlling "big-brother" hovering above the system.
Is the old-way were really that bad? How come PC's are getting slower and slower in spite of ever-faster electronics?
The mentioned shift from low-level Algo-crafting to higher and higher levels object-scripting resulted in less-and-less efficient runtimes, as the compilation of source-to-object gradually filled with more-and-more irrelevant garbage, influencing the size and speed of the running object. Comments anyone?
"Almost" Good Answers: