Because it's programmable. I'm a programmer. I like things to be programmable.
I've got no hope of remembering what a key like F6 means in a given context - it's a meaningless number. The Touch Bar lets me have context-sensitive keys I can actually understand and use.
This is not sufficient on its own. It's possible to have a programmable keyboard that has no screen. It's also possible to have a programmable screen that doesn't take over the function row (a row that has existed since the earliest days of computing).
> I've got no hope of remembering what a key like F6 means in a given context - it's a meaningless number
This doesn't make sense to me at all. Do you use keyboard shortcuts in the apps you use? How does Ctrl-Alt-Shift-V hit you? What about vim or emacs bindings?
We memorize a large number of things that are just as 'meaningless' as F6, so I'm struggling to get on board with this take.
> The Touch Bar lets me have context-sensitive keys I can actually understand and use.
As a touch typist, the changing context of a position on that row means I can no longer rely on my memory of the position of the key. I have to re-learn the meaning of that position for every app that uses that position for some other purpose.
For me, this is just as insurmountable as F6 is for you.
Not really. If they're presented to me via the Touch Bar then yes.
> How does Ctrl-Alt-Shift-V hit you?
Never heard of it! Doesn't sound very intuitive! What do all those keys mean and why are those in that order and how do you discover them? If it was on the Touch Bar I could just see the icon and discover it and learn the muscle memory.
> What about vim or emacs bindings?
But I don't use these editors. And why do they need special bindings anyway?
> We memorize a large number of things that are just as 'meaningless' as F6, so I'm struggling to get on board with this take.
Seems like it should be the computer's job to memorise things, not mine? I don't want to rote learn F6 = step-over in my debugger. That's not a good use of my time. I want an icon I can see when I look for a function key, then learn the muscle memory to keep hitting.
'F6' means nothing to me. Where am I supposed to look that up? In a manual? I don't want these kind of context-switches.
> As a touch typist, the changing context of a position on that row means I can no longer rely on my memory of the position of the key.
The keys don't move on the Touch Bar. If you're using muscle memory they're in the same place each time so you're fine and there's no problem!
Yes. Yes, you are meant to look up the keyboard shortcuts of software programs in their manual, or Google them, or otherwise RTFM. It's part of learning one's tools.
Speaking from personal experience, the critical importance of memorizing keyboard shortcuts was drilled into me by years of PC gaming as a kid and teen. (Imagine playing StarCraft with just the mouse... Ugh.) I wonder if people who grew up with computer games are more likely to embrace keyboard shortcuts later in life.
- [0] https://en.wikipedia.org/wiki/Optimus_Maximus_keyboard
