I hope that I didn't put off too many of my readers with my somewhat negative post about Windows PowerShell yesterday. It is not that I dislike PowerShell, it is just that I can't imagine using it often as a shell. But, this is certainly a matter of taste. Jeffrey Snover replied to my post in the Microsoft Windows PowerShell team blog putting forward an important argument for using PowerShell as a shell.
- Pip install Boto3 - Thu, Mar 24 2022
- Install Boto3 (AWS SDK for Python) in Visual Studio Code (VS Code) on Windows - Wed, Feb 23 2022
- Automatically mount an NVMe EBS volume in an EC2 Linux instance using fstab - Mon, Feb 21 2022
That said, I whole-heartily agree with Michael that if this is what you had to type that on the command line, that would be a pretty painful shell experience. But you don't. We designed a set of aliases, positional parameters, etc to allow a very pithy command line experience.
It is certainly true that aliases improve productivity if you often work on the command line. However, I still think that most tasks can be done faster with a good GUI tool and there are plenty of them for Windows. Every time you try to remember this nifty alias you used last time, you usually are already done with an easy-to-use GUI tool. To come back to the example in my previous post, if you have to manage Windows processes you probably will be faster in most cases with Process Explorer.
Most Windows admins I know will always use a GUI if they can. That's why I still have serious doubts that PowerShell will be used often as a shell. One thing is for sure, though, PowerShell will be an important scripting language.
Anyway, to make good my negative assessment, I want to link to a great new post about Windows PowerShell for IT Administrators. This article isn't another PowerShell documentation, but gives a good overview and some interesting background information. It also lists a couple of useful tools related to PowerShell.
Subscribe to 4sysops newsletter!
Update: I just saw another lengthy reply to my first PowerShell post. Please, check it out if you want read about a completely different view.