4 ms·
Since shell languages invariably end up becoming scripting languages (see: Bourne shell and resulting nightmare), Powershell targets being a good tool for both
by AnIdiotOnTheNet 9y ago
Since shell languages invariably end up becoming scripting languages (see: Bourne shell and resulting nightmare), Powershell targets being a good tool for both purposes.
When scripting and writing documentation, full commandlet names are encouraged:
Get-ChildItem | Where-Object { $_.Name.Contains("evidence") } | Remove-Item
When using the command line, there are built-in shortcuts (and users may define their own aliases):
gci | ?{ $_.name.contains("evidence") } | ri
For the convenience of those hopelessly entrenched in Bourne shell, there are some default aliases:
ls | ?{ $_.name.contains("evidence") } | rm
- stcredzero 9y agoSince shell languages invariably end up becoming scripting languages We need to start paying attention to this phenomenon.