3 ms·
You must really like powershell then. I love most of the language, but I'm convinced it was written by people who type 300 wpm.
by Aloha 2y ago
You must really like powershell then.
I love most of the language, but I'm convinced it was written by people who type 300 wpm.
- yjftsjthsd-h 2y agoI think powershell is meant to be tab-completed, more than typed at 300wpm? I still prefer terse, though; pretty sure I can type `tar xvf` faster than I can tab-complete `tar --extract --verbose --file`.
- Aloha 2y agoYeah, thats the issue, tab completion can only do so much.
- delta_p_delta_x 2y agoNot the parent commenter. I prefer PowerShell to any Unix shell. It can be tab-completed, including every cmdlet's parameter names. Writing PowerShell scripts is a delight. In fact I can write the core business logic in C#, VB, F#, or any other CLR language, and expose the shell logic with a thin PowerShell wrapper.
- dale_glass 2y agoYup. IMO PowerShell's decisions were right for the modern age, just like Unix's decisions were right for its age. Today terminals are fast and highly functional, memory is cheap, CPUs are blazing fast too. Our modern bottleneck is not the computer struggling to intake commands fast enough, but people struggling to understand what the heck Bob was trying to accomplish 3 years ago. And for that, a verbose scripting style that helps not need to look up every single parameter in the manual is very helpful.
- Aloha 2y agothe underlying issue, is that tab completion can only do so much.