Comparing DOS to NTVDM is absurd, without even mentioning PowerShell. One of the best new things in NTVDM is the innate ability to process lists in a FOR loop, making batch processing a cinch. Add to that the ability to use (and the improvement in) jscript, vbscript, and wscript (again, not even mentioning PowerShell), and there is no comparison whatsoever.
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.)
Good to know winders finally understands the concept of a 'for' loop.
It's hard to believe it's taken this long.
Too bad microsoft took so long to come to scripting table. (unix has had awesome scripting capabilities forever) Heck, even IBM DOS 7.0 had REXX, which was incredibly powerful. Especially since way back then, when I had either a 486 or maybe a Pentium, you could actually write a script in Rexx that would run on PCs running DOS, and OS/2, then take that same script and run it on an actual mainframe without changes.
$ scp data[1257]-a?.dat zeugma@foo.bar.com:mydata/.
(copy any file in the local directory that begin with "data" followed by any of the numbers 1,2,5 and 7, followed by "-a", followed by any one single character, ending with ".dat". Copy it to the remote system "foo.bar.com" using my 'zeugma' userid and put it into a subdirectory called "mydata" that is under zeugma's home directory.