Pre MacOS X was a 90s style OS and had major limitations that were a problem for every user, starting with no real multi-threading, and I think no protected memory.
Where it was great was in the simplicity to the user. If you wanted to install or uninstall a driver or functionality, all you had to do is move an extension file in or out of the extension folder and reboot. That simplicity was lost in MacOS X. That made simple users dumber. (and iOS went back to the simplicity)
> Pre MacOS X was a 90s style OS and had major limitations that were a problem for every user, starting with no real multi-threading, and I think no protected memory.
Technically, the last “classic” Mac OS had memory protection and a fully preemptive scheduler.
The very serious caveat was that all “classic” Mac OS applications ran in a single process, and, within it, were scheduled cooperatively.
It was possible to create fully preemptively scheduled threads from within such applications, but they couldn’t write to the screen. I don’t remember whether they could do file I/O.
No, even then it still isn't. A device should not protect you from making bad decisions. It should be an aid in making good choices, not a nanny keeping you safe because you can't be trusted to do better.
I think to the parents point, everything should be wide open, all the features possible, and let him configure. By not listening, isn't that 'over-simplifying', let the user decide.
Where it was great was in the simplicity to the user. If you wanted to install or uninstall a driver or functionality, all you had to do is move an extension file in or out of the extension folder and reboot. That simplicity was lost in MacOS X. That made simple users dumber. (and iOS went back to the simplicity)