I’ve been learning PowerShell recently and as I was writing down the good things about learning about a shell scripting language I came to this conclusion. I n

I’ve been learning PowerShell recently and as I was writing down the good things about learning about a shell scripting language I came to this conclusion. I normally use Python for things like this, but I have gotten burned more times than I care to admit with simple scripts having dependency issues. I realized that shell languages are not only smaller languages, but are more limited in scope. This means there are less dependency issues to handle. On top of that PowerShell scripts are easy to stitch together with pipes, so doing things like parallelizing and sending a job to the background as a task, then checking on it later is a lot easier. Furthermore the stitching together of shell feels very functional, and because the cmdlets only do one thing getting it to be parallelized is infinitely easier. To this day PowerShell is the only code I’ve ever parallelized on purpose. I then realized this was all possible due to the self contained nature of the cmdlets, which goes back to the Unix philosophy invented in 1969, about doing one thing and one thing well