3 ms·
> "why on earth would someone actually like the touchbar...ever?" Because it's programmable. I'm a programmer. I like things to be programmable. I've got no h
by chrisseaton 6y ago
> "why on earth would someone actually like the touchbar...ever?"
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.
- geerlingguy 6y agoBack in the ancient times, people would put overlays on their keyboards... some still do, for things like DAW editing stations, video editing, etc. :)
- eh9 6y agoCan’t wait for all the keys to be programmable screens that show shortcuts based on context.
- chrisseaton 6y agoYeah that'd probably be the best of all.
- cosmotic 6y agoI know what the commonly used F-keys do for tasks I perform often. They are just as context-sensitive as the touch bar, except they don't display the action on the key. You're trading that display for tactile feedback that there's a key there you can press and that the key press was registered. Seems like putting a screen in the keyboard would satisfy both, but wouldn't satisfy the slider use cases.
- haswell 6y agoThe Optimus Maximus [0] keyboard comes to mind. Pair this kind of tech with one or two dedicated slider controls placed somewhere else on the keyboard, and I think you have the best of both worlds. - [0] https://en.wikipedia.org/wiki/Optimus_Maximus_keyboard https://en.wikipedia.org/wiki/Optimus_Maximus_keyboard
- haswell 6y ago> Because it's programmable. I'm a programmer. I like things to be programmable. 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.
- chrisseaton 6y ago> Do you use keyboard shortcuts in the apps you use? 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!
- 6y ago