> I'll point out that many of these annoyances don't have equivalents on the command-line.
I'd argue the entire command line is nothing but annoyances. Everything is completely non-obvious and often requires reading man pages that can contain a hundred options that may or may not be in alphabetical order.
The fact people have to write scripts to really function on the command line is telling.
My personal nightmare is exiting vim. If I make a mistake typing, I enter recording mode instead of exiting. This happens to me several times per day. And, no it's not a matter of being more diligent, it's the result of a disability.
The command line is powerful and I absolutely love it but it is a pit of rusty razor blades people keep throwing ropes over. :)
The command line has suffered like everything else. Complexity creeps in and builds on itself. But scripts aren't the problem, scripts were part of the design as the intent was to glue together the many CLI utilities. Scripts bind them into performing a repeated task (versus one-offs).
I'd argue the entire command line is nothing but annoyances. Everything is completely non-obvious and often requires reading man pages that can contain a hundred options that may or may not be in alphabetical order.
The fact people have to write scripts to really function on the command line is telling.
My personal nightmare is exiting vim. If I make a mistake typing, I enter recording mode instead of exiting. This happens to me several times per day. And, no it's not a matter of being more diligent, it's the result of a disability.
The command line is powerful and I absolutely love it but it is a pit of rusty razor blades people keep throwing ropes over. :)