keymap-editor VS qmk-keymap

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

Yes, it is technically possible in QMK to record a history of the previous 2 keys (or more) to have a skipgram-reducing magic key. This is possible in QMK by saving the keycode for each event in a sliding buffer. See my example on triggering based on previously typed keys and the source for my Sentence Case for implementations of such a key history buffer. I see u/mEFErqlg shared an implementation as well in another comment thread.

I really appreciate all the work that's going into ZMK, and am by no means an expert on the limitations or architecture that they're working within, but personally feel that the recent macro-parameter implementation fails to elevate the Behavior[3] into a sufficiently powerful construct. I'm trying to imagine how it could offer greater composition and control over an invoked sequence of keycodes, key-positions, and behaviors, but if that ever comes to be, it will be on the shoulders of giants. Development has been very active, and the contributers have all done great work. Shoutout to zmk-nodefree-config[4] and thumbkey[5] for android, which has also been under rapid development from a wide group of contributers (special thx to WadeWT and sslater11, amoung many others).

[1]: https://github.com/getreuer/qmk-keymap/

Check out my keymap. My intention is to put a rather light load on the thumbs. Lately I've been doing this:

Uses getreuer's 400 entry autocorrect dictionary. https://github.com/getreuer/qmk-keymap/blob/main/features/autocorrection_dict_extra.txt

A cool thing with QMK is that you may insert arbitrary C code to handle key events. That's a lot of power, and I've been having fun with that. Check out my keymap. Some gems:

Please pull or re-download getreuer/qmk-keymap to get the latest.

I am a software engineer and use a 65% as my daily driver. 65% is enough for the most common keys including a number row on the a base layer, and I have special symbols and F-keys on a symbol layer (see my keymap). For me, the point of mechanical keyboards is ergonomics, and on that front I suggest a split, columnar keyboard with QMK or other programmable firmware. Here is a brief features tour of why I think these keyboards are so awesome.

I'm a software engineer and naturally spend a lot of my time at the computer writing code, plus quite a bit of non-code writing (emails, reviews, ...). Since RSI is something of an occupational hazard, mechanical keyboards are for me mainly about preventative ergonomics and comfort. Though, writing custom code within QMK keymap has interesting productive possibilities... I've been having fun with that.

You want fun experimental features?—check out my QMK repo =)