The Woes of PowerShell
medium.com
medium.com
As someone with ~medium unix terminal knowledge, I frequently grow frustrated with the lack of such functionality in windows. I was excited to learn about Powershell, but alas it is too different. It's meant to pass objects around and not stream text, so you can do some really hard stuff, but it makes a lot of the easy stuff a lot more cumbersome. It's also glacially slow and yes, getting up to speed with it is a never ending stream of errors that are hard to make sense of.
When it works, it's great, but I find that it is rarely the ideal solution.
Not true. If on path, name is enough. If not, you ./ or .\ it.
> Omitting the & means PowerShell will simply print the name of the program you want to run.
Yeah, because its not a program but a string. Basics.
> So it’d make sense that PowerShell scripts end in .psh. In fact they end in .ps1
Weird complaint
> Apparently there’s no equivalent for less?
Yes, there is equivalent: https://community.chocolatey.org/packages/Less
> For example there is a command to retrieve the AuthentiCode signature on an executable but none which hashes a file (shasum).
Get-FileHash: https://docs.microsoft.com/en-us/powershell/module/microsoft...
> The command set PowerShell has is not a perfect match for what UNIX provides
How can it be a perfect match ? Its a different shell of different paradigm. Also, many linux aliases are removed starting from pwsh era so they don't block native tools.
> but trying to use it interactively like a UNIX shell will end in immediate and total failure
Mind blown
That complaint doesn't even make any sense. `less` is a standalone utility; it has nothing to do with the shell.