VBScript deprecation: Timelines and next steps
techcommunity.microsoft.com
VBScript deprecation: Timelines and next steps
1–10 of 75 posts
Re: VBScript deprecation: Timelines and next steps
#2> Notably, these browsers have never implemented support for VBScript.
This reads mildly accusatory and got a chuckle out of me.
I'm surprised it took them this long!
Re: VBScript deprecation: Timelines and next steps
#3Probably one of the most maddening things I have ever worked with, and that is saying something. Though a huge part of the blame for that goes to COM and registration, interop stuff, which is more Windows than VBScript and also probably never truly going away.
Re: VBScript deprecation: Timelines and next steps
#4[deleted]
Re: VBScript deprecation: Timelines and next steps
#5> Notably, these browsers have never implemented support for VBScript. This reads mildly accusatory and got a chuckle out of me. I'm surprised it took them this long!
Folks who complain about Javascript don't realise how close we were to having vbscript as the dominant web language
Re: VBScript deprecation: Timelines and next steps
#6> Notably, these browsers have never implemented support for VBScript. This reads mildly accusatory and got a chuckle out of me. I'm surprised it took them this long!
Folks who complain about Javascript don't realise how close we were to having vbscript as the dominant web language
yeah we should have a language that was built in a day instead of a week. move fast.
Re: VBScript deprecation: Timelines and next steps
#7I find PowerShell, the language, verbose and not very ergonomic. This ship has sailed, but I wish Microsoft had done something to make Windows automation a little closer to other platforms, so that it could benefit from the good software that exists on other platforms.
It seems that VBA will continue to exist as the programming front end for MS Office, which is unfortunate. They had announced Python support for Excel a while back and I wish it was better promoted as a viable VBA replacement.
Re: VBScript deprecation: Timelines and next steps
#8I find PowerShell, the language, verbose and not very ergonomic. This ship has sailed, but I wish Microsoft had done something to make Windows automation a little closer to other platforms, so that it could benefit from the good software that exists on other platforms. It seems that VBA will continue to exist as the programming front end for MS Office, which is unfortunate. They had announced Python support for Excel…
PowerShell is terrible. The idea is good, the implementation bad
Re: VBScript deprecation: Timelines and next steps
#9I find PowerShell, the language, verbose and not very ergonomic. This ship has sailed, but I wish Microsoft had done something to make Windows automation a little closer to other platforms, so that it could benefit from the good software that exists on other platforms. It seems that VBA will continue to exist as the programming front end for MS Office, which is unfortunate. They had announced Python support for Excel…
A deep chill ran down my spine as I remember all of those VBA tools I updated/generated during my first internship... some of those are still being used in some semi-industrial applications.....
Re: VBScript deprecation: Timelines and next steps
#10I find PowerShell, the language, verbose and not very ergonomic. This ship has sailed, but I wish Microsoft had done something to make Windows automation a little closer to other platforms, so that it could benefit from the good software that exists on other platforms. It seems that VBA will continue to exist as the programming front end for MS Office, which is unfortunate. They had announced Python support for Excel…
Yeah, I like the ideas behind PS, but Nushell implements them so much better (it's yet to be stabilized though)