| | As a Hewlett-Packard Systems Engineer for a number of years, I was trained in Operating Systems theory. I also did sophisticated software / application development on them. Mainframes, minicomputers, etc. The OS's not only had to multitask, assign priorities, assess security, but entire businesses, all the endeavors of giant corporations, much more complex than today's PC environments, depended on them both in batch and t/p mode. Yet these computers were dependable. They basically didn't crash or freeze or grind to a halt under time-sharing or transaction pressure (although this last is not entirely an OS issue).
With the advent of poorly designed PC Operating Systems - led in large part by the PC-DOS kluge Mr. Gates bought and messed up further, which came to be called "Windows" - you now see these problems - and many others - regularly.
Also, Windows was developed in an insecure and almost criminally irresponsible manner. No operating system not designed by idiots needs to be vulnerable to viruses and malware or being taken over by outsiders who use them as bots or 'slave' computers.
You simply don't allow outside software, whether buried in webpages or jpegs or email or from any other source to run or gain administrator level security without permission.
Not every computer problem is in the software (people can breach security, leave files unprotected, use stupid passoards). But a lot of it is. When I was in computers, I looked at and sometimes had to fix a lot of code. Poor design. Stupidly, ineptly written software written in a hurry, failing to account for eventualities.
I'm old school. I believe each new generation of software, including OS's, ought to run -much- better and with fewer glitches than the preceding.
*Especially* operating systems like Windows. They are the air traffic controllers, the executive programs which run/allow/prioritize everything else that flies and lands.
(Edited by Philip Coates on 2/08, 9:11am)
|
|