5 ms·
Finally! I love the methodology behind PowerShell. It's more verbose than bash, and that's OK to me. The readability and _consistency_ far outweigh the extra ch
by electricEmu 10y ago
Finally! I love the methodology behind PowerShell. It's more verbose than bash, and that's OK to me. The readability and _consistency_ far outweigh the extra characters. Now, I get that coupled with all the flexibility of *nix tooling.
It's going to be a long road to hook everything up, but this has the chance to finally standardize command parameters.
I'm sorry. This is truly amazing to me and I'm quite excited!
- cbaleanu 10y agoI Can Only See One Problem With PowerShell :)
- ghostly_s 10y agoIt's happy to gobble up whatever improperly-capitalized cmdlets you throw at it, heck you can even forget some letters ;). And with a little tap on that tab key it will helpfully fix your laziness so there's no trace of it in your shell history.
- electricEmu 10y agoSo, that's kind of the beauty to me. For long lived scripts I can always type out `ForEach-Object { ... }`. When I'm ad-hocing there's always `%{ ... }`. Bash is a strange beauty, but part of that beauty is how arcane it can be. Generally, people use the smallest parameter possible in scripts instead of the full name. While this can definitely continue with PS, the community has decided on "alias for ADHOC and Full-Name for scripts". This helps the readability tons if someone hasn't memorized all the command parameters.
- noveltyaccount 10y agoPowershell is case-insensitive, so feel free to avoid that shift key if you're so inclined :)
- cbaleanu 10y agoBeen using PS for a long time and I had no idea about this. Thanks !