I wouldn't take it that way. That's the thing about Windows: until Powershell was developed you basically couldn't do scripting worth a hill of beans. CMD was basically useful for setting a few things up to go off at a certain time and doing simple file rename/copy/move/delete chores, but any more sophisticated scripting was out of the question.
I'll take exception to that - I love the DOS/CMD environment... I am probably to be considered native there. It is a different approach than bash, but that doesn't make that approach invalid.
One of my complaints in learning to live with *nix is the plethora of arcane switches built into the executables - Yes the executables are far more powerful, inevitably, there are many switches in each one that I will never use. But so many options were very hard for me to remember - even to this day, I have to hit the man pages to figure out what I want anything to do.
DOS, and later CMD, are not as robust - that is certainly true. But I find cmd to be more usable on the fly, because I DO know (in my head) it's capabilities. And what grew out of the Win/DOS ecosystem, was a less deliberate, but more facile way - I don't expect the cmd line to do all I want - I write what I want and add that to the basic system. Every DOShead I know has an extensive toy box somewhere on the PATH. Some of those are staples in the DOS community (Schaeffer's WBAT was in my kit from DOS 6 through to XP SP-2) others are custom (I wrote LSTFile.exe specifically as a list processing tool and bang-counter, and like many others, I also wrote an INIFile.exe as a means of accessing, changing, and remembering storable options.)
Now, all that makes for a less portable system - One has to be ever aware of dependencies (and break your batches if they are not found) and there is a big problem keeping up with the OS - I had over 300 batches and executables break over the DOS to NT switch in Win2k, and the same happened again in XP SP-2...
But even with that, I much prefer DOS/CMD. I find powershell to be just as cumbersome as bash is. Maybe that's because my environment is so very customized to the way I do things - It is very personalized to !ME! I prefer that to conforming myself to thinking that I don't naturally define for myself.
So in summary, like I said, I don't think one or the other is superior - They are different, with different mindsets - Somehow, I was able, for all those many years, to work script magic in DOS and CMD to make it do things no one thought it could. Even today, there's a cmd box open at all times - And the tools I write tend to be in the no man's land, with one foot in Windows and the other on the cmdline.
