4 ms·
This is correct. The thing is, powershell is not for humans. It is purposed more towards configuration and system scipting, and thus should be compared to somet
by demosito666 8y ago
This is correct. The thing is, powershell is not for humans. It is purposed more towards configuration and system scipting, and thus should be compared to something like ansible. Using it as a shell is counter-productive unless you have very specific mindset.
Unix shell, on the other hand, is a trade-off: it offers you options to process and automate and reasonable convenience when working interactively. None of those aspects is perfect, of course, but it allows gradual learning curve (i.e. being able to do quick and dirty things from the beginning), is much more versatile and ubiquitous.
- deleted 8y ago[deleted]
- h1d 8y agoWho is going to write "configuration and system scipting" if it isn't for humans? Ansible playbook reads very easily to humans.
- demosito666 8y agoTry to run it interactively :)
- krylon 8y agoAt work, I always keep a PowerShell instance open. I like the fact that many common commands have Unix-like aliases, plus a lot of server software offers PowerShell interfaces for administration (e.g. Exchange, VSphere, SharePoint, ...). On Windows, I strongly prefer PowerShell for interactive work, although I cringe a little each time I see how much memory it uses.