I think the FOR /<x> command is an area where bat/cmd wins over VBS.
In VBS there's no easy way of enumerating an entire folder tree unless you dabble in recursion. This would of course mean some overhead in translation and procedure call setup.
Isn't it just much simpler to do something like
Try doing the equivalent of the following but in VBS
FOR /R %a in (.) do @echo %a
Command subsitution is another area. You could shell out and pipe to a file but it's just so much easier to do
FOR /F (tokens=1,2 delims=,) %%a IN (userlist.txt) DO @ECHO User name is %%a. Full name is %%b
These are really trivial examples but to do the same thing in VBS would take lots of lines, especially the file management (texts treams, arrays, read line, split, manip, join, write line, blah, blah, blah.... do me a favour!)
FOR /F %%a IN ('dir /b') DO @ECHO %%a
My challenge to VBS coders. Write a script to archive all the INI files on the C: drive using NT Backup which will be the only external program you are allowed to call.
Now I'm not saying there should be an exclusive choice between BAT/CMD and VBS( or JS for that matter). VBS offers more control but in some situations it can be qutie cumbersome.