3 ms·
But the different "modes" of anything are just the state of the input mechanism. To be clear, my argument is not to use modes for the sake of using modes. Mor
by taeric 14y ago
But the different "modes" of anything are just the state of the input mechanism. To be clear, my argument is not to use modes for the sake of using modes. More that I do not understand the attitude in computer design where it is assumed that we can get down to no modes in an interface. There is this magical "all context switches to get here do not count." That is, it is a fine guideline, but treated as its own independent rule is missing all of the conflict and tradeoffs that actually go into many decisions where they arise.
Editors are an amusing example, because they come up a lot. But, for many, getting the computer to the damned editor is enough of a mode change that it is hard to do.
With GUI applications, the march lately has been to hide as many of the "buttons" as possible. Which is not really doable while still adding buttons. This is the same problem as faced by car interface designers. Even the iPod did this. "Spinning" back then was either selection or volume control, you know, depending on the mode. :)
So, yes, I agree excessive modes are bad. I even agree that vim is a bad interface for most folks. (Most being everyone else I know that uses a computer, honestly.) I disagree that "modes are bad" is at all a useful mantra by itself. It is only helpful when you take all of the other context into consideration, as well.
That make sense? (As far as the "better" interface for a car, this one is easy to imagine. Come up with an interface where you really just tell the car what it is you are wanting to do. "Take me to the store." "Pick up my daughter from school." ...)