MicrosoftVBScript must stay! System Administration is much easier with VBScript, we used it many times for system administration.
Look how strange Powershell looks for sysadmins:
Instead of:
a = 23 > 12 and 12 > 40
You have to write in Powershell:
$a = 23 -gt 12 -and 12 -gt 40
And to convert the number 13 to a currency:
a = CCUR(13)
You have to do in Powershell a crazy stunt like this:
$a = "{0:C}" -f 13
This is crazy to learn, nobody wants that and Microsoft should start to understand that users want a SIMPLE, EASY Language for System administration!
It's definitively NOT Powershell, you can push that as long as you want, SysAdmins will NEVER ever love it!
I ask Microsoft to keep VBScript, maybe add some security layers.
If you must remove it from WSH, then please update the JavaScript module in WSH so that it supports modern JavaScript!
Another way for Microsoft would be to include Python into WSH.
WSH is a great way to let users extend Applications with scripts. And that MUST stay.
And, noneless to say, many business applications rely on WSH+VBScript, we have now to rewrite much much code to JavaScript which is a big big present from you Microsoft!
Do you, Microsoft, think, we developers have too much freetime?
I guess you know the answer...
just keep VBScript and the beloved WSH which extends so many critical business applications, that have now to be rewritten.
I ask you, Microsoft, to go back to your roots, and to keep focus on DEVELOPERS, DEVELOPERS, DEVELOPERS!
Because we make you big!
