What's /g/ opinion on Powershell ?

It has its uses. There's very little reason to write scripts for batch anymore. Legacy support is probably the most notable. Any other way and you're faster off with Powershell.

However if need fast interaction with cli applications then batch is still superior.

>>55696791
S L O W
L
O
W

VeryLongOpinionBecauseThatsHowEveryoneWriteItAndClaimItReadable

>>55696835

>However if need fast interaction with cli applications then batch is still superior.
How so? Powershell is perfectly fine for interop with CLI applications.

>>55696882
It's a shell language. Shells are not known for performance.

Power shell is best shell

Bash fags don't know what they're missing

>>55697717
>How so? Powershell is perfectly fine for interop with CLI applications.

Pipeline in Powershell works differently from that in cmd. So pipeline between two CLI applications will fail.
The solution is to call cmd command from within Powershell and let it execute the pipeline. OR use .Net and invoke StandardOutput and StandardInput objects of each CLI application, but it's way more messy.

It's good, but in the end it's just another trick to get you to use Windows.

The worst part is that I fell for it.

The main problem I have with powershell is the Long-IncrediblyVerboseCommands

>>55699094
Then use aliases.

I wore out the fucking tab key... but besides that, it's alright

Useful for windows automation and not much else.