4 ms·
> Also would anyone recommend learning how to use Windows PowerShell and again would that have the same kind of insane learning curve? I do have to use Powersh
by outworlder 11y ago
> Also would anyone recommend learning how to use Windows PowerShell and again would that have the same kind of insane learning curve?
I do have to use Powershell at work so I am familiar with it. But you can't seriously claim that Powershell is an example of good design. Its language is as inconsistent as Bash, even with the benefit of hindsight.
Powershell is only helpful with the flags and switches, if you are calling other powershell scripts, or .net libraries. If you are calling standard executables, you are back to square one. Which happens to be bash's more common use case.
- useerup 11y agoPowerShell is miles ahead of bash, sh, ksh, zsh etc when it comes to consistency. For instance: * All of the cmdlets follow the same verb-noun pattern. * There are only 40 or so standardized verbs, with guidelines for what they should be used for and how to choose the nouns. * Parameter names are also standardized * Parameters are parsed by the shell - not individual commands, which means that all cmdlets take parameters the same way, no strange differences like between dd, ls, find etc. * There's a set of standard parameters supplied by the shell that is common to all cmdlets, and which has the same function on all cmdlets (-ErrorAction, -WarningAction, etc). * Cmdlets are more single-purpose than typical unix commands. Take for instance unix "find". Why can a find command delete files and why can it execute other commands?? * PowerShell supplies scripting and expressions. Meaning that there no need for tools such as jq, awk, find, xargs etc, each with their own expression syntax.
- lawpoop 11y agoThanks for the write-up, this is very informative.