4 ms·
You try doing any reasonable data processing with PowerShell and it will use a lot of resources. You can accomplish a lot with awk. I was a PowerShell advocate
by mickotron 6y ago
You try doing any reasonable data processing with PowerShell and it will use a lot of resources. You can accomplish a lot with awk.
I was a PowerShell advocate but it still has a lot of rough edges which is disappointing. And is very verbose. Sometimes grep | awk can be incredibly succinct and fast.
- majkinetor 6y agoNot sure what you mean because it uses dot.net regex. Sure, its way more generally resource hungry then awk but again, it does tone of things. Its also good to know that you have that power ASAP on Windows and without any extra toolson *nix such as awk or jq or sed. I regularly handle 100MB files with Powershell regex , yeah, I wait few seconds here and there, but nothing except ripgrep handles this fast. Verbosity is nonsensical arugment for anything as you have alises. Bash is equally verbose if you use long parameter names.