MicrosoftSo many issues with this. As an earlier post here asked, what about the many millions of installations created using .msi installers that use vbscript? They won't be able to update their software or uninstall. We have a very large installed user base and some of them can take months to authorize even the tiniest changes (think U.S. military, nuclear plant operators just as two examples).
In more general terms, the whole "this is about security" angle is, to me, nonsense. When was the last major malware spread using vbscript? If any exist, even the worst antivirus product would catch-and-kill in an instant. It's a non-threat.
And most important, whither IIS? Our site is 100% vbscript not JavaScript and has stayed that way because of the vast number of folks that use stuff like noscript and many other ways to disable JavaScript. Server-side vbscript should not be destroyed in this whole process.
