DOS Lives!
DOS Lives!
"The more things change the more they stay the same." is an oft-used quote: because it's true.
The Microsoft .NET® offering from the initial version to the 2005 version (lousy name BTW, causes typesetters and typers all sort of grammar checking problems) is going back to the roots of DOS® - Disk Operating System - that was the mainstay of the 1980s and early 1990s.
How can I say that?
Well, the concept of the "new" .NET world is that everything is self contained application where the configuration, code, working environment all stays together using web.config and ini files - wait! That's what DOS had: config.sys, autoexec.bat and ini files to control the setup environment that an application ran in - each app customized them so they would run correctly.
The only difference between DOS and .NET is that now the applications run in their own separate managed memory spaces - no QEMM 386 manager to shim on top of DOS and config.sys conflicts to worry about. The OS is just better now at ensuring no memory conflicts.
Thus, .NET is really not inventing anything new - they are just recycling the DOS way of doing system configuration using new file names of the old DOS system configuration files doing the same darn thing.
The Microsoft .NET® offering from the initial version to the 2005 version (lousy name BTW, causes typesetters and typers all sort of grammar checking problems) is going back to the roots of DOS® - Disk Operating System - that was the mainstay of the 1980s and early 1990s.
How can I say that?
Well, the concept of the "new" .NET world is that everything is self contained application where the configuration, code, working environment all stays together using web.config and ini files - wait! That's what DOS had: config.sys, autoexec.bat and ini files to control the setup environment that an application ran in - each app customized them so they would run correctly.
The only difference between DOS and .NET is that now the applications run in their own separate managed memory spaces - no QEMM 386 manager to shim on top of DOS and config.sys conflicts to worry about. The OS is just better now at ensuring no memory conflicts.
Thus, .NET is really not inventing anything new - they are just recycling the DOS way of doing system configuration using new file names of the old DOS system configuration files doing the same darn thing.
In a related note: Humans are the first task switching operating system. Humans cannot multi-task - they really task switch from one item to another just like a computer does. All computers task switch - the computer just does it so fast that it appears to be doing multiple things at the same time.
posted by Tom Philo at 9:20 AM
0 Comments:
Post a Comment
<< Home