Should I Make My Script In Batch or PowerShell

[SgtD0nuts]

I am making a new script for debloating Windows 10, I am into debloating Windows. Is there any advantage to using one over the other. My past scripts was written in PowerShell, but does Batch offer anything.

 

[Lordmage]

PS make for the easiest for the system to understand and for other users to use and is usually the goto for those things.

 

Batch scripting would be a waste of time IMHO.  

 

[SgtD0nuts]

yeah, your right

 

my past scripts were written in PowerShell, and I know PowerShell pretty well. Just wondering if batch had anything to offer, but no it has nothing to offer.

[mMontana]

Powershell is far more powerful than batch.

[Hi P]

On 9/10/2023 at 5:48 AM, MrBignose5866 said:

I am making a new script for debloating Windows 10, I am into debloating Windows. Is there any advantage to using one over the other. My past scripts was written in PowerShell, but does Batch offer anything.

 

Truthfully, you are better off using PowerShell on Windows.

Bash (among other shells) are more common on Linux environments.

 

"X is far more powerful than Y"  -  is nonsense like : "Boots are better than Shoes"

It pretty much depends on your skill, a tool can offer as much as your skill set.

 

It depends

 

Edit: I misread the word, but I will leave my post as is

[WWicket]

Quote

Bash (among other shells) are more common on Linux environments.

Unclear if you are just bringing up Bash as another popular scripting option (and I suppose maybe a weird possibility with WSL) or if you misunderstood because batch and bash are similar words, but the OP is talking Windows batch scripting, which is unrelated to Bash. 

 

Quote

Just wondering if batch had anything to offer, but no it has nothing to offer.

It has significantly better predictability (don't need to worry about interpreter versions) and backwards compatibility. Sometimes in enterprise environments you need to write a script that will work on computers that might not have PS or might have the wrong PS version etc. *cough DOS* Batch script can be lighter and the interpreter significantly lighter than PS. In most cases, PS is a much better choice, but that doesn't mean batch has nothing to offer/ is never the right choice.

For your specific example, if you want to make your debloater be able to work on systems that have PS disabled, than PS is obviously the wrong choice (Or if you wanted to also support older versions of Windows [95/98/ME/2000]).  Not much but something

[wanderingfool2]

Everything I would say is "it depends"

 

There are some things that I think creating bat files are just more beneficial.  The ease and quickness that you can quickly see a simple bat and know what approx it is doing.

 

The other thing is that bat files will run on pretty much any computer; where as ps you can't just "run" it without having to put in a longer cmd prompt (at work I would use a prompt to launch all my ps scripts).

 

Don't get me wrong, ps is a great tool and if you are familiar with it then might as well keep using it over bat....but I do think that bat files are greatly overlooked

 

One thing I still use them commonly for is anything that needs parsing of files...like I could do something like

 

ffmpeg -i %1 [additional params] d:\temp\output.mp4

 

and just drag a file onto the bat and have it create my desired file.  Quick and simple...in PS it wouldn't be as simple as this kind of one liner

[Hi P]

21 hours ago, WWicket said:

Unclear if you are just bringing up Bash as another popular scripting option (and I suppose maybe a weird possibility with WSL) or if you misunderstood because batch and bash are similar words, but the OP is talking Windows batch scripting, which is unrelated to Bash.

I absolutely misread the word! I thought we were talking about Bash or PowerShell (since if I recall correctly, there's a way to run Bash on Windows)

 

Shame on me hehe