3 ms·
Layer violations are way easier in OSes that don't have memory protection. For example, in classical Mac OS, it wasn't unheard of, and actually fairly common, t
by Someone 13y ago
Layer violations are way easier in OSes that don't have memory protection. For example, in classical Mac OS, it wasn't unheard of, and actually fairly common, to have a driver write into video memory to give user feedback or even to have a driver pop up an alert, or to have an application move the mouse pointer by writing the appropriate memory locations in the kernel.
Historically, it was even worse: all desk accessories on Mac OS where running as load able drivers (http://www.folklore.org/StoryView.py?story=Desk_Ornaments.txt http://www.folklore.org/StoryView.py?story=Desk_Ornaments.tx.... Aside: that article shows that Jobs did actually design a GUI, that for the calculator. More info at http://www.folklore.org/StoryView.py?project=Macintosh&story=Calculator_Construction_Set.txt http://www.folklore.org/StoryView.py?project=Macintosh&story...)
I think windows wasn't much different. There is/was an article about the mess that Microsoft's build system for Windows was that explains how they spent lots of effort fixing layer violations in order to improve build times (they used to have full builds only novice every few months. That meant that incompatibilities between, say, an improved menu system and the latest version of the Explorer would take months to surface). Anybody remember that?