[washadjeffmad]

"Low" is the right idea for me.

When I buy (or build) a kb, I have the expectation to be able to tell it how to operate; that's why I needed it, after all. I find it tedious to remap lots of keybindings (was super+... global? shit.) when I can simply assign 24-48 non-conflicting commands to function keys.

Some map to scripts, others to specific actions in the tools I use, some are used to turn on cameras, switch users, chance resolutions, pull all logs, push commands to restart devices in VMs or bring up or take down containers, start or stop services, reset PCI or storage devices, or semi-automate git. It's really whatever I want to press a button and make happen. It was much worse when I first got clever with udev and dbus years and years ago.

I've always hated clicking and menu-hunting. If I know what I want to do, I don't want to wade through someone else's idea of UX to get to it.

Abjure the cruft. Embrace Function.

[chrisseaton]

> I have the expectation to be able to tell it how to operate

This isn’t a reasonable expectation! Use the product as it’s designed! Work with it not against it!

> I find it tedious to remap lots of keybindings

Well don’t do this then. Why make things so complicated and custom?

[ashtonkem]

I mean, you can add your own things to the Touch Bar for such tasks, but you’re already pushing the limits of any laptop keyboard. At that point you’re better off using something with programmable firmware, not the built in.