keyboards VS miryoku

I have custom alpha layers and extremely optimized symbol layers, combos and other features in my keymap. It is not designed for web development, but it is good for VIM and Java.

That made me think. If I would adapt Romak for 20 keys, it would be something like this:

But since you are a programmer, I invite you to check the fancy programmer features that I have implemented in my keymap. I still need to rework on the documentation, but you can take some inspiration from there if you decide to design your own.

Romak also has some very nice attributes, as do poqtea and uciea. I also find Canary to have a lot of merit.

There is also the unusual option to handwire a keyboard without soldering, as I did here, but the result might not be so reliable.

You can see my layout here.

I started my own layout, Romak, using BEAKL as inspiration, with similar objectives, mostly making it more suitable for my home language and reducing the load on pinkies and indexes, concentrating in the middle and ring fingers instead. Another thing I did was to remove the top row key from both the central and pinkie columns. Later I also removed the bottom row key from the pinkies.

My first handwired board checks all your requirements, and I have some pictures of the process, but it is not a complete guide. It might help though. And I think the FFKB case can be great for a first handwired project.

Really nice work, congrats. My custom layout is designed for both Portuguese and English, and I have some of the same ideas implemented, with similar reasoning. I also have some programming features that remind yours, but I preferred to remap hjkl instead.

I've used two different options in my builds. You can see them in the build logs: FFKB and Rommana.

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.