WoW has the ability to redefine the user interface through keyboard short-cuts, LUA code, and UX changes. There is an active community providing different takes on the UX.
WoW has a built in 'time test' which consists of 'boss' encounters in what the game calls a 'raid'. [1]
In polling characters who were better able to perform during an encounter, there was a strong correlation between "keyboard" users and better performace. Better was defined as able to respond faster and more consistently to changing conditions.
It would be interesting to have Tog have a look.
[1] For anyone not familiar with WoW and its gameplay, a group of 10 or 25 people, of different specialties (game specific; damage doers, healers, and damage takers (tanks)) who coordinate during an encounter with a powerful game character (a boss) by fighting it. Healers are focussed on applying various skills to keep the players alive (they take damage due to various game mechanics), damage doers (dps) use different skills to maximize their damage, and tanks use their skills to keep the game characters focussed on attacking them rather than the other players. After a set amount of time, the game character 'enrages' which basically makes it impossible to kill and it does 10x the amount of damage it normally does. This results in a 'wipe' (all player characters in the group dying).
Professional Starcraft 2 players need to use hotkeys because they have to be able to do multiple tasks at once - they're macroing with their left hand while clicking around the mini-map and performing other tasks with their mouse hand. You couldn't play SC2 (well) with just the keyboard or just the mouse.
As for the muscle memory for mouse movements, there's no question that Pro SC2 players have exactly that. If you watch a pro give his opening workers commands, it looks like what he's doing should be impossible. You or I couldn't sit down at a computer and do it. But they can precisely because of muscle memory: they know how far a mineral node is from the starting base and exactly what mouse movements are needed to select a worker and send him to a specific mineral patch, then select the next and so on. It's true that in Starcraft 1 this muscle memory was even more necessary as SC2 has automated (to a high degree) many tasks that once required precisely practiced mouse movements, but you still see SC2 players using those skills that they learned from Brood War.
All good WoW players bind all their skills to keys rather than clicking them because if they didn't do that they couldn't use that skill while running, or while selecting a new target. It's not about the cost (or lack thereof) of mode-switching between keyboard/mouse, or the cost (or lack thereof) of consciously manipulating the UI -- it's purely about being able to walk and chew gum at the same time.
That's not the 'mouse being vital', that's 'missing out on keystrokes' and putting a keyboard on the mouse.
Semantic games are fun but unless you're actually contesting that the mouse is vital you're just tilting at straw men.
For the record I own one of the weird things Microsoft built the 'Strategic Commander' [1] which, if one could have two of them, and the protocol was documented, my make for an interesting test platform.
[1] http://www.google.com/products/catalog?q=gaming+mice&um=...] [2] http://www.google.com/products/catalog?q=gaming+mice&um=...
However, I believe there is "muscle memory" that can be learned using the mouse. For example, playing a lot of first person shooter games in my day, one can learn and memorize the nuances of moving the mouse. Correlating the amount and direction of movement of the mouse with the response of the screen is, I believe, a skill that can be learned and is quite rewarding.
What happens is that a mouse-friendly interface is organized in such a way that finding the right action to click on involves traversing a tree of choices. Even if you memorize the exact location of the action you want in that tree, for many actions you still need several clicks to perform something instead of just one.
And that's not the end of it - you clearly need keyboard input too, in many cases. For example in WYSIWYG editors, you type-type-type, then you need a new header, move your hand on the mouse, select the right header in the select-box (during which your eyes also move from the current line), then get back your hand in typing position and start typing again, until you need another mouse action.
This is the reason I wrote my last resume in HTML and didn't even bother opening office, even though HTML sucks for typography (I'll probably switch to Latex next time).
That said, the mouse is better for browsing around, exploring stuff or for interfaces such as Photoshop. I also don't mind the mouse for interfaces where I don't need to be productive. Someone mentioned CAD in this thread - I disagree as AutoCAD is more productive with keyboard input.
Elsewhere, you actually have to click on things. Personally, I find that that takes up a huge amount of cognitive space.
Wasn't it back around that same time period that some people also tried playing FPS games with a joystick? Probably would have worked ok for Doom, but I can't see it working as well with anything that allows vertical aiming.
What I'd like to see as an experiment is having a much finer grained control over your keyboard sensitivity.
As an example, let's say you have "a" mapped as your left turn (not strafe) key. So pressing and holding "a" gives you the standard movement speed you've come to expect. Pretty terrible.
Now let's say holding shift and pressing "a" gives you a turn speed that's twice as fast. Already this is a pretty significant improvement and offers you some control over you turn speed using only the keyboard.
Now let's add a couple more modifiers; crtl/cmd for 3x speed, alt/opt for 4x speed. Let's also add some new keys for turn 90 degrees, turn 180 degrees, turn 270 degrees, and these are all instant, just like a fast mouse turn.
A mouse still allows for much more granular control when it comes to aiming etc. but for someone who spends to time to really adapt these keys it would close the gap significantly and may even make keyboard aiming / turning a viable option.
I could be completely wrong though and it might just feel terrible, but I'd love to test it out to see.
This is why I like Opera so much.
I don't mind using the mouse so much as I do moving my hand from my keyboard to the mouse and back.
It's also an incredibly powerful addon when you dig down into what you can do with it. Last I checked (which was quite a while ago, to be fair), Vimium sadly didn't have the more technical aspects, but it's pretty much equal for keyboard browsing.
I think there's also a big difference in the amount of physical effort needed when using the mouse. With the keyboard it's easier to keep most of my arms relaxed, and when I need to switch to the mouse everything from the shoulder down has to contract into action.
That said, I live in emacs and spend most of my day on the keyboard. Maybe I'm doing it wrong in a way that only works for limited mouse use.
Maybe that's why I hate Windows so much -- the position of the menu bar, for example, means I have to stop and think to pull menu items in a way that I never have to on the Mac (thanks to Fitt's law). Similarly, the over-reliance on toolbars and ribbons.
> Unlike the keyboard, the mouse scarcely rewards learning at all
I find it hilarious watching experienced vi and emacs folks furiously typing macros to perform text operations that are trivial with a mouse or graphical editor. The problem isn't that the mouse doesn't reward learning, but that what you learn is harder to define.
There is also the aspect that the only time my hands hurt, or I experience carpal tunnel symptoms is when using the mouse extensively (especially when gaming). I have never had pain when using the keyboard.
Sure. Never mind that mediocre Starcraft players like me can perform about 100 mouse actions per minute of the sort you just described.
That argument really doesn't match reality anymore.
Are there any other examples I'm missing?
Twitter, Github and Kalimba¹ are the ones I can immediately recall.
¹Kalimba is Embedly's HN frontend, very nice for quickly going through stories: http://hn.embed.ly/
Before mouse gestures, yes, I would have agreed with that text, but not now. I genuinely browse faster with just the mouse and the gestures than with only keyboard, or with mouse+keyboard without gestures.
Note: the Chrome gestures plug-in is not up to the quality of the Opera native implementation. There's no comparison.
I find mouse clicking as much "muscle memory" as using the keyboard; changing the position of buttons and items causes issues. For example, when I upgraded to Firefox 4, accessing bookmarks was moved, and for a few days I didn't automatically bring up HN without thinking.
See also: https://secure.wikimedia.org/wikipedia/en/wiki/Flow_(psychol...
That's a very good term. I've often seen it applied to commuting, for largely the same reasons.
This is because operating a mouse-based user interface is a conscious process - one which cannot be fully relegated to "muscle memory." Unlike the keyboard, the mouse scarcely rewards learning at all.
Erik Naggum, in a Usenet post (circa 1997) explains this far better than I could:
"The clumsiness of people who have to engage their brain at every step is unbearably painful to watch, at least to me, and that's what the novice-friendly software makes people do, because there's no elegance in them, it's just a mass of features to be learned by rote... it's sadly obvious that we are moving into a way of working that is predominantly _conscious_, for which I believe the human brain was never prepared. we no longer have the time to let skills sink into the autonomous nervous system, as it were, and even if we try, the criminal in Redmond, WA, has a new, incompatible version out by the time we learned the last version... One of the joys of learning to ride a bicycle is to stop thinking about it -- the feeling that I had successfully programmed my body to master a bicycle at least thrilled me as a kid (except I didn't know the verb "to program")... we need to communicate to users that learning to use Emacs is like learning to ride a bicycle -- it does take some time and effort, it's a worth-while skill to have, and then you never forget. I firmly believe that the novice-friendly software is like giving people several sets of supporting wheels so they won't tilt, but could get moving right away, and then never taking them off, preferring that they keep using them and moving so slowly that they always need them. of course, if you argue that they should remove the supporting wheels to such users, they will, admittedly correctly, argue that they will fall _splat_ on the ground and ruin their three-piece suits. clearly a no-go."
(http://groups.google.com/group/comp.emacs/msg/821a0f04bab918...)