samoklava VS miryoku

Thanks! I should have been clear but I was talking about this project that's a fork of the main : https://github.com/soundmonster/samoklava

You might have to go down the path of making your own boards, I started off based on this: https://github.com/soundmonster/samoklava It's a good resource to minimize the amount of work you have to do on kicad

There’s only one autorouter that’s a) open source and b) known to work. It’s called FreeRouting. I’ve tried to adapt it for a GitHub workflow that takes an Ergogen YAML and outputs ready-for-fab PCB Gerber files. It doesn’t work perfectly for all use cases, so it’s probably worth double-checking the result with a DRC (design rule check) run in KiCad. Watch out for shorts and opens! 🤞

I used this Ergogen-based keyboard (samoklava), plus Chocorne's layout, as a basis for mine

There’s a board called ‘samoklava’ which is pretty corne-like , just with a bit wider thumb-splay and pinky-stagger https://github.com/soundmonster/samoklava

There is samoklava and rae-dux, and you can look through the layouts listed in this comparison tool for more. As for ones with a trackball, the Charybdis and its nano variant come to mind.

18 let half, wireless: https://github.com/soundmonster/samoklava

It's like completely generated and autorouted. Amazing. https://github.com/soundmonster/samoklava

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.