4 ms·
To me, the difference between using a command-driven tool and a graphical interface is comparable to the difference between explaining a native speaker how to g
by Yetanfou 11y ago
To me, the difference between using a command-driven tool and a graphical interface is comparable to the difference between explaining a native speaker how to get to the museum (straight-on for 200 m, second turn left, first turn right after the park) and trying to do the same to someone who does not understand any of the languages I speak by pointing, making walking movements with my hands, mimicking left and right-hand turns and trying to find a way to bring across the concept of a park by these means.
Yes, I had to learn German, English, Swedish and French before I could converse with people using those languages. This took time, but it was well worth the effort. It took time to learn (eg.) vi as well, but this too was worth the effort. I can still point and click my way through a maze of menus if I want by using a GUI-enabled version of vi or any other editor, but why bother when I can just tell the thing what I want in a few keystrokes?
- oldmanjay 11y agoI suppose you could use one of the thousands of GUI-based editors that also have key shortcuts for their commands. I don't know which one you used that required menu navigation to do everything you should name-and-shame so we know to avoid it.
- splawn 11y agoUnless you are talking about emacs and/or vi bindings, the key shortcuts you are talking about are just barely scratching the surface.