[deleted]
VBScript deprecation: Timelines and next steps
21–30 of 75 posts
Re: VBScript deprecation: Timelines and next steps
#22So far I have avoided Powershell in anything distributed to end users, because execution of unsigned scripts is disabled by default in Windows. It has been easier to use VBScript or BAT files to automate basic tasks, since those scripts can be run unsigned... I suppose it is too much to hope for that Microsoft would now reconsider enabling Powershell script execution by default.
Re: VBScript deprecation: Timelines and next steps
#23I 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…
I don’t like the verbosity either, but have come to appreciate it as a cross-platform scripting tool for technical people who aren’t programmers. Again, it’s verbose, but more approachable for these new users than unix scripting languages. Being able to run scripts on macOS and Linux is a bonus. Given all this, I’ve come to peace with PowerShell.
Re: VBScript deprecation: Timelines and next steps
#24Earlier quoted context omitted.
It may have a separate timeline but it does seem to hint at going out the door in similar order on Office as well. I think the Python in Excel stuff is still in beta but things like lambdas, regex or Office Scripts all actually work (even on the web versions) and start taking big bites out of why you'd want to look at VB. New Outlook dropped VB support even on the desktop and I don't think they plan on maintaining se…
Python in Excel could have been amazing, except Microsoft executes it in a cloud environment and require a Cloud Service account to even open spreadsheets with it in. I'd strongly recommend people avoid Python in Excel, it is a Trojan Horse into forcing you to subscribe to access your own spreadsheets.
It’s ironic that Microsoft was founded to provide software for microcomputers where the whole idea was that you own the CPU and don’t need to pay anyone or ask permission for access.
And now they’re full circle back to mandating the timeshare computing model even though the local CPU has incredible performance.
Maybe they should rename to Centralsoft.
Re: VBScript deprecation: Timelines and next steps
#25Earlier quoted context omitted.
Python in Excel could have been amazing, except Microsoft executes it in a cloud environment and require a Cloud Service account to even open spreadsheets with it in. I'd strongly recommend people avoid Python in Excel, it is a Trojan Horse into forcing you to subscribe to access your own spreadsheets.
It’s ironic that Microsoft was founded to provide software for microcomputers where the whole idea was that you own the CPU and don’t need to pay anyone or ask permission for access. And now they’re full circle back to mandating the timeshare computing model even though the local CPU has incredible performance. Maybe they should rename to Centralsoft.
[flagged]
Re: VBScript deprecation: Timelines and next steps
#26I know lots of software products which use VBScript to realize application scripting
Re: VBScript deprecation: Timelines and next steps
#27I 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.....
No worries, they probably haven't updated Excel since you left.
Re: VBScript deprecation: Timelines and next steps
#28I know lots of software products which use VBScript to realize application scripting
Can you share some?
Re: VBScript deprecation: Timelines and next steps
#29I 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
PowerShell is amazing
Re: VBScript deprecation: Timelines and next steps
#30I 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…
With WSL2, is there any objective reason to write new Powershell scripts in 2024? I am genuinely curious because I barely have used Windows these days and had some brief experience with WSL2.