2 ms·
> Although, PowerShell is effectively self-documenting, which is good for busy sysadmins. Oh no it isn't. Very basic stuff like Get-Something piped into a Remo
by sofixa 5y ago
> Although, PowerShell is effectively self-documenting, which is good for busy sysadmins.
Oh no it isn't. Very basic stuff like Get-Something piped into a Remove-Something is, but beyond that, it gets complex quick. Add aliases, weird logic and limitations ( do you know you can't break out of a Foreach-Object?), and it quickly becomes an illegible mess that needs parsing, the same way Python might.
Furthermore, a lot depends on the cmdlet provider, and for instance the VMware ones are steaming piles of horseshit with inconsistent naming of parameters, broken async, and useless error management ( e.g. you get an error which says to check the inner exception, but it's empty and there's no way to get any detail whatsoever).
- kaba0 5y agoI would still take that over the cryptic -fHxC magic incantations of unix tools. Especially that you get unified help for all of them, readily available. And I say that as someone who really doesn’t like windows (and thinks it is not fit for development at all) — but powershell is really a gem, if one gets over the at first strange syntax and actually looks into it.
- throwaheyy 5y agoThe first paragraph is just sloppy coding practices which can render any scripting language, not solely Powershell, illegible.
- majkinetor 5y ago> do you know you can't break out of a Foreach-Object? I don't because you can. > Furthermore, a lot depends on the cmdlet provider, WTF, bash is unusable unless grep, sed, awk and friends are present .
- delusional 5y ago> WTF, bash is unusable unless grep, sed, awk and friends are present. No one is calling bash self documenting, so that comparison doesn't mean anything.