VBScript deprecation: Timelines and next steps

Bruce Neiman  : There are indeed obviously no plan "B". Javascript scripting technologies in Windows and runtimes are EcmaScript 3, and Naveen_Shankar  recommendation to use this is just pure bull...thing.
He surely never programmed a complete business app in JScript or VBScript. We, developers, do it. Every day. Because these technologies are incredibly simple and powerful.

Young cost-killers not even born when Classic ASP was invented were happy to find a job at Microsoft.
Then, one day, they decided to deprecate VBScript, simply because "it could look cool" and reassure investors in regards to "Microsoft high commitment into end-users privacy and security".
Deprecations are a way to communicate publicly.

Erasing the past is the way they have chosen to do so (a sort of technical "cancel-culture").

Completely counter-intuitive, that decision will explode in their face as surely than other major catastrophic events in this company's memory :

1. Internet Explorer antitrust prosecute
2. Steve Ballmer as CEO
3. The Windows Phone
4. Add VBScript and Classic ASP deprecation to this list? NO! A BIG NO!

Security arguments are weak motivations: every antivirus knows how to block "harmful" Office macros and dangerous VBScripts for almost 15 years.

Why not remove and deprecate Microsoft SysInternals Suite tools?
After all, they are old, ugly. But they are useful. Exactly like Classic ASP.

Talking about the SysInternals tools makes me think: time has come for https://azure.microsoft.com/en-us/blog/author/mark-russinovich/ to jump in the game.

Every 7 days, 10 people (Classic ASP Developers and VBScript SysAdmins) sign https://chng.it/LVZG5XXGsK.
Far for disminishing, this number is constant from this petition's launch: Why? Well, we already all know why. This has been explained by everyone on this post.

Seriously, should we have the specialized tech IT magazines to jump in the game and make a bad press to Microsoft on this one, too?
That scenario is just so simple to avoid if MS simply just reconsiders this absurd position.

There are rational people at Microsoft, and Mark is one of them.

• Noone better than Mark knows how widely spread is VBScript usage in the Windows Server Administrators ecosystem.
• Noone better than him knows what disaster it will be if VBScript and Classic ASP engines would be wiped out.

Mark is a living memory, still alive and kicking.
He knew the "world before", and is deeply involved in the "world after".