> To run a program from the PowerShell command line, you must start with an & symbol. Not true. If on path, name is enough. If not, you ./ or .\ it. > Omittin

> To run a program from the PowerShell command line, you must start with an & symbol. 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 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.powershell.utility/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