4 ms·
Powershell had potential, but it didn't pan out. It's annoying and very challenging to remember all the one-off flags. With bash, you only need to learn 10 or
by metadat 2y ago
Powershell had potential, but it didn't pan out. It's annoying and very challenging to remember all the one-off flags.
With bash, you only need to learn 10 or 20 short commands and a few flag variants, over a gently long period of time. Then you're all set for 97% of cases likely to be encountered.
- ants_everywhere 2y agoI just wrote a two line bash script to process some large csv files that Python/Pandas were taking far too long to process [0]. A lot of people (myself included) tend to underestimate the power of the heavily optimized GNU utilities and the ability to manipulate them with bash. [0] It was two lines for readability. It could have easily been a single line.
- partdavid 2y agoThis is the opposite of how I see it. There's really nothing universal about flags, especially short ones, in different random utilities (what's -n mean? -f? file, filter or force?). Whereas in Powershell since there actually is some standardization, your knowledge about what -WhatIf or -Verbose do is actually pretty leverageable. And more powerful with the ability set default parameters and so forth. And the discoverability and help in Powershell is also standardized. So I get why unfamiliarity would make it not worth it to switch from whatever shell you prefer, but I don't think I can see your point about flags.