GUI do democratise access to capabilities, but unless you work only with pixels GUIs are inferior in every single way.
GUI do democratise access to capabilities, but unless you work only with pixels GUIs are inferior in every single way.
Except in the way that matters: symbolic representation and manipulation (and discoverability).
>Expressiveness is not limited to a medium, and if you ever used a command line interface you would understand the concept it pipes and arguments is way more expressive than a round of 100 clicks to do the same thing thru a GUI.
Actually, a GUI can trivially include a pipe system (tons of VFX and Color gradings apps for example offer one, MAX/MSP and others).
A GUI can also trivially include a text console, and have all the capabilities of the command line.
The command line, on the other hand, can't have all the capabilities of the GUI. Even auto-completion is implemented crudely with curses interfaces (which, in any case, are GUIs too).
(Oh, and I've been using the command line since the pre-Solaris days of Sun OS).
That's a good one, I've been using Unix/Linux systems daily since the early 90s and test people on their Bash skills in job interviews.
You are essentially arguing the same point Jobs is emphasising. If Jobs have to do it your way, basically you are leaving behind 95% of normal people who are not tech savvy like writers, artists, accountants etc who could benefit from a computer without knowing the complicated inner workings of a computer. Exactly the same way you are benefiting from `ncurses` and not writing all the obsure logic of text rendering from scratch everytime just so you can work in command line ... You misinterpreted this whole discussion as an argument between GUI vs terminals which is not the point at all.
Most people need ease of use more than they need raw power. Both of them have their place.