keymap-editor VS miryoku

The difference is: https://nickcoutsos.github.io/keymap-editor/ Click the firmware generated button which takes you directly to the action tab for the latest build. Then clicking to download firmware.

Looks nice. I can recommend the following graphical configurator: https://github.com/nickcoutsos/keymap-editor

I haven't looked into QMK configurators because if I go to the trouble of building a keeb I'd go all out and make it wireless. I did look at [keymap editor](https://github.com/nickcoutsos/keymap-editor) for ZMK, which could be close enough to Oryx for me to try sometime.

The only other thing I could recommend in that case is custom built; it's easier than you'd think, and some people have made GUI interfaces for ZMK like this: https://github.com/nickcoutsos/keymap-editor

I know ZMK does not have an official one, but there's one that uses github actions in order to build a firmware for you after you commit your keymap. That's probably the closest we'll have to zmk configurator for a while https://github.com/nickcoutsos/keymap-editor

I think the closest thing at the moment is https://github.com/nickcoutsos/keymap-editor.

Looking forwards: the chosen bootloader should support over-the-air updates, and GUI front-ends for ZMK do exist, albeit with varying maturity. 1 2

I've seen https://github.com/manna-harbour/miryoku but it doesn't appear to be easily modified.

A 75% keyboard still require quite a lot of wrist movement, which is not ideal in your situation. It's better to learn to use layers, you could still have all the function keys and such with a 36 or 34 keys. With with such a small keyboard you don't need to move your wrist while typing. A Corne or even a Ferris Sweep can do the job with a proper keymap, like Miryoku.

If you prefer to have semicolon on Base you'd substitute custom Base, Nav, and Sym layers, swapping semicolon and slash, with https://github.com/manna-harbour/miryoku/discussions/85.

The Miryoku layout [1] has a dedicated number layer which turns the left half into a number pad. Practical (once you get used to it) and portable.

[1] https://github.com/manna-harbour/miryoku

It's understandable if some people would prefer a larger layout. I wouldn't argue people should be using smaller keyboards.

It's "I don't mind moving my hand to hit the key" vs "I don't mind holding down some Fn key to hit the key". (Or with F1-F12 on Macbooks, you need to both hold down a Fn key and move your hand).

For an example of "36 keys ... how", I think the popular miryoku layout is fascinating. https://github.com/manna-harbour/miryoku/tree/master/docs/re... -- Often, mnemonics for particular keys aren't all that complicated.

Except for those who use Miryoku, which is not optimized for software development, probably every single person here will have its own custom keymap.

The keyboard on the other desk is a wireless Corne low profile kit I built up a while back using a couple nice!nano controllers and their low power display too. For general typing I don't have much of a problem going back and forth between the two, but the Corne is only 34 keys and I use a complex layout called Miryoku to get access to most symbols and functions I have by default on my 360.