16 ms·
I can't get past the first part. Modes aren't bad. Indeed, modes can be used to great benefit. The only problem with modes is one of discoverability. It can
by taeric 14y ago
I can't get past the first part. Modes aren't bad. Indeed, modes can be used to great benefit. The only problem with modes is one of discoverability. It can be difficult to know what mode you are in at times, as well knowing of the different modes available.
Of course, this is essentially true of the entire god damned computer experience. Knowing what programs, or modes, available is not an easy task for many to undertake.
To think that you can simplify your model of computers to the point that you can eliminate modes is to simplify your model to the point that it is useless for a great many things.
And to think that timed modes is bad misses an essential point. The vast majority of users do not want to be in these extra modes. Returning to a "default covers 99.999% of the users" is far from a bad thing. Of course, the first lesson many should be taught, but aren't, is not how to find these modes. Rather, it is how to completely reset the system to defaults.
And yes.... I'm a vim user.
- rraval 14y agoIf you read the Wikipedia article that the author linked to in that assertion[1], you'll find that it mostly agrees with you: > In Raskin's sense and according to his definition, an interface is not modal as long as the user is fully aware of its current state. Given this definition, eliminating modes is as simple as making sure that the user is aware of what mode they are in at all times. This makes your assertion problematic: > To think that you can simplify your model of computers to the point that you can eliminate modes is to simplify your model to the point that it is useless for a great many things. I don't think you would argue against the notion that users should be made aware of what mode they are in. A pretty common example comes from the CSS `cursor` property: - If its `default`, clicking should have no effect - If its `pointer`, clicking should have an effect - If its `move`, clicking and dragging should have an effect These cues are far from useless and help transition a modal interface into a modeless one. [1] http://en.wikipedia.org/wiki/Mode_(computer_interface) http://en.wikipedia.org/wiki/Mode_(computer_interface)
- deleted 14y ago[deleted]
- rraval 14y agoAs long as you make sure that the mode vim is in the user's locus of attention. Typically, a user is more focused on the actual text they are trying to edit and thus the vim mode falls out of their locus of attention. So it's not just about displaying what mode the system is in but also making sure that the user is always aware of the mode. It's this mismatch that make modal interfaces bad. Edit: Parent has since deleted their comment. It used to say something along the lines of: > So if I make vim always display the mode its in, does that make it modeless?
- cjh_ 14y agoGood points, displaying the mode isn't enough as you cannot guarantee that the point of display will be sufficient to keep the mode as the user's locus of attention. In vim I get around this by habit, I stay in command mode and only enter insert mode for text entry, and then at the end of a 'unit' of text entry I return to command mode. Thus I always know when I am in insert or command mode by asking 'am I currently entering text', for me hitting ctrl-c after finishing a sentence is part of the act of writing the sentence.
- rraval 14y agoOh totally, I'm a fellow vim user myself and do exactly as you do. But have you ever had Caps Lock on by accident in normal mode? Most confusing 3 seconds of my life.
- cjh_ 14y agohaha yes, very common to the point where I no longer have a capslock key (my keyboard is programmable, so I nuked it).
- shurcooL 14y agoModes are mostly bad when there is no feedback that you're in a given mode. If there's plenty of feedback, it's fine. Think of your currently active app on a mobile device. It's a mode. But if you're in Chrome, you will not accidentally open a link instead of drawing a line because you thought you were in SketchBookX.
- tomphoolery 14y agoI'm also a Vim user, and this bit stuck out to me somewhat: The problem with modes is that you are not constantly aware of the current mode, which leads to errors: you want to draw a line, but accidentally create a gradient fill. In Photoshop, where it is somewhat difficult (at least it was for me anyway) to understand which mode you were in at any given point, this kind of problem does exist. But hypothetically, suppose you could always be aware of which mode you were editing in? Would modal interfaces still pose the same sorts of problems? I definitely agree with Ilya on his assertion that modal interfaces are bad news when other factors of the situation require you to not pay attention to the interface, for example a car's computer or a mobile phone. I find it incredibly frustrating when the interface I'm forced to use is giving me shit, because it jeopardizes my safety while driving. I've learned over the years when to just "put it down", and to always have backup CD music in my car in case my lovely iPhone which can play any track ever made (if I have a decent LTE connection) decides that it's just not going to do that today. In most situations, it seems that a modal or even timed-modal user interface is not what you want, and certainly not the most efficient use of brainpower for your device. On the other hand, given that someone is aware of his mode at all times, modal interfaces do give an extraordinary level of efficiency to even simple interfaces. Ilya's "TV Remote" analogy is a perfect example of this. A remote isn't something you need to use while in motion, nor is it typically something that is lunged for, grabbed, and acted upon very quickly as a response to something insane happening around you (like a gun, for example). I think it would be preferred to have a remote with less buttons and more modes, with very clear ways of knowing which mode you're in. The vim-powerline plugin (for my favorite text editor) is a perfect example of this, I can know what mode I'm in simply by being aware of the color of the bottom bar in Vim. It would require devices with far less complexity, instead of needing a dedicated control for each and every action you take. I think Native Instruments' MASCHINE, a groovebox and hardware/software production studio, does a very good job with this. There are few times, except early on, where you are unaware of which mode you are in. It was designed for live performance as well as home studio usage, so its interface is very simple, yet very complex at the same time. It has dedicated controls for parts of the song that always need to be adjustable (for example, volume/tempo/swing control), and defaults to "performance mode" where the easiest thing to do right off the bat is start banging out beats or melodies. There are other "edit modes" which let you write new parts in a step sequencer, record live beat mashing or sample-fuckery, and adjust effect processing for damn near everything, but access to these modes require a level of "intent", wherein you need to definitely know you're in that mode. It's also very easy to see when you're in a given mode, because the dual LCD interface is so simple that it's very easy to tell that you're in the wrong place. Wow, that was a lot. Sorry if it's a big mash of paragraphs but I really am fascinated with UI and UX creation.
- mmahemoff 14y agoI'm using Chrome right now, that's a mode. I'm in HN tab right now, that's a mode. I'm editing a textarea, that's a mode. All these are legitimate "modes" in the sense they dictate what happens next when I type or click. The real advice is to be mindful of modes and make users aware of which mode(s) they're in. Sometimes they help, sometimes they don't.
- deleted 14y ago[deleted]
- rektide 14y agoIn this set up: I'm using Debian right now (to run Chrome), that's a mode. I'm using Xen right now (to run Debian), that's a mode. And yes, these are captive, modal systems. But from a UI point we have to take some strata as granted, as operating system level. Yes, perhaps Debian is a modal interface, whether it's hosting Xorg or Mir or Wayland or KMSCon or ssh sessions. But these are host environments for the proper interface, and so is gdm or slim or lightdm running my X session, and so is openbox or kde or gnome-shell or awesome running my wm, and so is chrome running my browser. These are all concatenative contexts providing strata for the application. They are modal systems, but notably every one of them exists to provide an amodal system for the host of services running underneath it. Amodality still has to derive functionality from some greater level, so the distinction I think your not encompassing is one of composition versus aggregation. In composition something owns and dictates the interface. In aggregation things contribute to available interface options. If I wanted to, I could have a media player running and control it via global hotkeys. If I wanted to, I could open multiple chrome windows. If I wanted to, I could open multiple tabs perhaps across multiple windows (Awesome powers activate). If I had multi-pointer-X and a good browser I could edit multiple text boxes. In contrast, when we talk about modal UI the discussion is around UI that captures the context. It locks out other modes of operations. Modal systems do not provide aggregate strata into sub-systems running under them, they lock out other sub-system from running. Amodal systems contribute capabilities to users. I'd like to find a way to loop back around and describe MDI as contextual without being modal (on the grounds that it's the same mode repeated), but I don't think I have sufficient argumentation to press that far ahead. I feel on firmer grounds taking issue with your characterization of what really is modal by standing on the aggregation versus composition point, and by highlighting the concatenative nature of the systems you describe.
- SomeCallMeTim 14y ago>And yes.... I'm a vim user. Yes, it was that obvious. But there are piles of UI design research studies that show modal interfaces are, in fact, bad. Objectively bad. Measurably bad. I get sick of the vim apologists who try to claim that vim has a good UI. It is objectively, measurably, terrible. Granted, once you've learned it, you can be amazingly productive. But the power of a program is completely orthogonal to how good of a UI design it has; the latter pretty much has to include discoverability. In the words of one of the current foremost user interface design experts, a "good user interface shouldn't require instructions." (-- Donald Norman) I use vim when I'm doing editing on terminals. I'm not a vim expert, and I don't intend to ever become one. It's far more efficient to get my file locally and edit it in my flashy GUI editor if I have to do serious development on it, than it would be to become that level of expert at vim. And I'm basing this on the many stories I've heard, written by vim experts, about how much work it is to get good at vim. Continue to use vim, by all means; you've climbed the hill and you know it, so it will be more productive for you than anything I could point you at to compare it to. But please, please stop trying to claim it has a "good" user interface. Both vim and Emacs have interfaces designed before any serious work was done on human interface design, and like the microwaves and VCRs designed back then, their interfaces are measurably, objectively terrible. Modern editors can do 99% of what a 3+ year expert in vim can do, but you can get to that 99% in a month or less. Just because you had to spend three years of your life to get to your current level of productivity doesn't mean you should haze new developers the same way.
- derleth 14y ago> But there are piles of UI design research studies that show modal interfaces are, in fact, bad. Then how do Vim users work? If they're doing something that doesn't let them work, how do they work? Or is that not what you were saying? Then what the Hell were you saying, and how is it relevant?
- TheZenPsycho 14y agoIt is fully possible for humans to adapt to terrible computer interfaces. That doesn't mean the interface is not terrible, it just means that humans are adaptable.
- demetrius 14y agoVim is often called a modal editor, but I think it in fact has fever modes than GUI editors. In vim, I usually need only 2 modes (command, insert). In Notepad, each menu is a mode of its own right (File, Edit, Format, Help)... And to get as feature-full as VIM, editors will need much more ad-hoc modes. I think vim's strength is not being modal. Its strength is having less modes than other editors.