VBScript deprecation: Timelines and next steps

So MUCH clear and argumented alerts and warnings now have been sent to Microsoft team members responsible of VBScript, VBA, Classic ASP, IIS, Components (FileSystemObject, Regexp, WMIC). The vast majority of them have been redacted by professional developers responsible of the continuity of their client's systems they designed.

These alerts clearly underline the impossibility to port/migrate/rewrite a lot of applications running the web, running businesses worldwide, and whose millions of people jobs (means of subsistence) depends on.

Times are tough. Yes new tools are available (.NET, Node.Js, …), but many crisis are in-place in the world, and more are raising everywhere (economy, geopolitics, ecology, finance): Please Microsoft don't be the one that will add another critical one.

In addition to the countless alerts written in this post, some very interesting one were written in the comments section of the https://www.change.org/p/ask-microsoft-to-cancel-their-planned-deprecation-of-vbscript-classic-asp to keep VBScript and Classic ASP alive, and are very well written and documented. You should definitely read them. And please, Naveen_Shankar  , follow them up to the MS people responsible of VBScript, VBA, and Classic ASP/IIS.

Too much large systems (CRM's, custom-made apps) were built with VBScript, VBA macros, Classic ASP scripts, and FSO/Regexp components so that their migration will be impossible, even in the next 10 years, even with the best will — although the cost won't be absorbable, leading these businesses to inevitable failure, with dramatic consequences (economy, jobs, critical processes in vertical and horizontal businesses, transportation infrastructures, health services, government and administration files, real human lives).

Ok, these tools were used for more than their "official lifetime", and for a good reason: they were neatly designed, still fulfill the needs of business cases, and they do not pose immediate risks and problems : keeping them available at least as a Feature-On-Demand (FOD) now just seems to be the only viable and acceptable official Microsoft Position.

That decision will calm down everyone, and Microsoft will serenely continue to devote resources to .NET, AI, Cloud and whatever else it wants, without having Classic ASP and VBScript harming them. On the contrary: such a position will keep developers happy, and keep them with a good opinion towards Microsoft, encouraging them to use the full range of other services offered by the company now and in the future.

Past is not to be opposed to Future.