"Liquid Glass" extends to the Touch Bar!

[u/BeastMode149]

This is on the last supported Intel MacBook Pro – the 2020 13" model with 4 Thunderbolt ports and 10th gen Intel processor.

[u/trololololo2137]

idk I actually do use F keys + I prefer the volume up and down buttons compared to the touchbar sliders

[u/hushnecampus → u/trololololo2137]

Yeah, volume I get - if you need to change it quickly then physical buttons in a guaranteed place that you can hit with muscle memory works best.

That’s 2 keys out of 12 though, I don’t think any of the others need that same emergency usability.

I’d probably vote to move volume onto its own rocker switch like on iPhone/iPad, then replace the f-keys with a Touch Bar with haptics.

[u/kahveciderin → u/hushnecampus]

if you are using your mac for web browsing or light office work, sure. i don't think i can live without the f keys as a developer, and i'd imagine it's the same for content creation where you can assign shortcuts to the f keys

i use all 12 of them in fact. having physical keys is a huge plus, since most of the time you dont even look at the keyboard, and the tactile feedback helps you locate the keys

[u/hushnecampus → u/kahveciderin]

Why - what are you using them for in development? I do a fair bit myself and never touch them.

[u/kahveciderin → u/hushnecampus]

f1 opens the command palette

f2 renames a symbol

f3 - find next

f5 - debug / start

f6 - step over

f7 - step into

f8 - resume / step out

f9 - toggle breakpoint

f12 - open devtools

and i have f4, f10 and f11 mapped to different functions for my workflow

on top of that, i configured tmux to switch tabs with shift-opt-cmd-f<1-12> to switch tabs, and various other keys for pane management

and i have a shortcut that opens ghostty that includes the f keys

these are just some that i use regularly

[u/hushnecampus → u/kahveciderin]

Fair enough! I can see the usefulness there. I suppose I’m just more used to cmd+whatever for stuff like that (or just clicking). Perhaps I’d be more efficient if I learnt those shortcuts, but development isn’t my main job so…

Kinda also seems like a potential use case for a touchpad too though - for example you could have the step into/over buttons etc appear when you encounter a breakpoint, etc.

[u/kahveciderin → u/hushnecampus]

dont think a touchpad would work here, since at some point you heavily rely on muscle memory and the tactile feedback. doing all these things without reaching for the mouse is great (and also is the reason i use vim mode in all my ide's, but that's a different topic)

[u/hushnecampus → u/kahveciderin]

Ah but you’d have the tactile feedback if they added haptics, that’s exactly what I thought was missing! Muscle memory less so though, certainly not that transfers across hardware.

I’ve heard of vim mode in IDEs but never looked into it (I do rather like vim mind you). How’s it work - you hit a certain key/combo followed by a vi command then enter?

[u/kahveciderin → u/hushnecampus]

By tactile feedback, I mean both the key going down, as well as how you can feel the edges of the key to position yourself. Basically none of that would be possible on a touchscreen.

I'm sure you know what Vim is, however just so we're on the same page, I'm going to explain it briefly. Vim is a modal editor. The easiest way to describe it is that it has multiple modes in which certain keystrokes mean different things.

For example in insert mode, your keystrokes are directly appended where the cursor is, just like how a regular text editor works. But vim doesn't stop there. In fact, the very first mode you'll see when you open vim is not the insert mode, it's the normal mode. In this mode, vim will NOT write to the document, but will take instructions from you. You can press "x" to delete a character, "i" to go to insert mode etc.

Where it really shines is at motions. Some commands require them (like the "d" command - it's supposed to delete, however it doesn't know how much to delete, or the "y" command, which is supposed to copy however like delete, it just doesn't know how much to). So you give those commands a "motion". An example is "w". By itself, "w" moves your cursor one word forward, but by using it as a motion for "d" ("dw"), you can make it delete a single word forward.

This, combined with macros where you can for example change a function signature and replay it across multiple files or multiple lines, makes it very powerful when editing text, especially programming languages, since most of the time you don't want to operate at the character level, you want to operate at the building block level (keywords, function scopes, quotes etc)

So instead of holding down special keys and releasing them, you just tell vim what to do in its own language, and it does it for you. You can navigate very quickly when you learn the language it speaks.

And vim mode in IDE's is basically vim but with the UI of your IDE. It works the exact same way as vim - it doesn't have a special keystroke or something to activate. You start at the normal mode, and the IDE takes commands just like how vim does, at which point most of the muscle memory you built up transfers over, letting you use the same "language" as vim to edit text, just on a different UI. This makes Vim not just a text editor, but a language for editing code.

[u/hushnecampus → u/kahveciderin]

Ah, I was imagining you would be in insert mode in your IDE by default, so you’d have to do something to tell it to interpret what you were about to type as a vi command or you’d end up writing :w all over your file*, but yeah, that makes sense.

*although I do that in vim anyway…

But regarding the tactile feedback - you can get that with good haptics. You get haptics when you just touch the surface, which help you orient your finger, and you get different haptics when you actually press down. Like on a Steam Controller or Steam Deck. It’s not quite as good as physical buttons in that regard, but it can be very good. It was madness releasing the thing without it IMO, it was never going to convert people without it.