And yet you mention it twice. I was comparing Windows to early Windows (even if I got the early date wrong. And I ran Windows 1.0) So tell me, where are batch queues, with user modifiable priorities, permissions, ownership, etc? A FOR loop has been known since the dawn of programming languages. Batch queues have been known for 40 years or more. Manipulation/management of running processes for as long. Windows yesterday and today is MSDOS with pictures. (Exaggeration.)
And yet you mention it twice.
Because it is really worth mention - PowerShell puts NTVDM to shame almost as much as NTVDM puts DOS to shame.
I was comparing Windows to early Windows (even if I got the early date wrong. And I ran Windows 1.0)
Fine - but the core serious work is still a comparison of the Windows DOS console v. NTVDM - The console is the meat and potatoes of OS power, and there is *no* comparison between DOS and NTVDM consoles.
So tell me, where are batch queues, with user modifiable priorities, permissions, ownership, etc?
Easy enough to do anything you want with a script and task scheduler (which can be called from the script, or the script called through the task scheduler...) I can set such things up with only Windows console tools and pretty much batch scripting, though my preference would be to use external tools for convenience (ie: inifile read/write capability, which is possible to do with on-board console tools, but not worth the effort).
A FOR loop has been known since the dawn of programming languages. Batch queues have been known for 40 years or more. Manipulation/management of running processes for as long.
I know that - I've been around since DOS 3 - It is what you can DO with the FOR loop... A DOS FOR cannot come close to what an NTVDM FOR can do - even knowing all the 'stupid DOS tricks'... And almost all the NTVDM console tools are likewise juiced up comparatively. I am a DOS *nut*, but there is almost no instance where I would prefer to be scripting in DOS over NTVDM. NTVDM is much more powerful, and one can easily manipulate running processes, etc... I can't think of anything in the system that I cannot do from the cmdline, with the exception of manipulating actual windows and positioning... But VBScript and Wscript can handle that.
Windows yesterday and today is MSDOS with pictures. (Exaggeration.)
If that were true, all my DOS based scripts (over 300 of them) and all my BASIC scripts would still run today... most of them broke in Win2k, and what isn't broke is generally deprecated, since on-board tools can do it better. The only thing I wish I had was an interface for the user (pictures) instead of only console - there is a vast wasteland between the console and the desktop - I had to write an app as a batch helper to bridge that gap, using html as a front end for batch scripts. But if you don't mind a console, Windows is highly manageable.