piantor VS miryoku

There are a few things that are close: * The Cantor/Piantor: more aggressive stagger and slightly changed thumb cluster. * The Swept Corne: essentially a big sweep. * The Hillside 46/48: This comes in many forms which are very similar to what you are looking for. Essentially an extra aggressive stagger (and perhaps splayed) Corne with a bigger thumb cluster.

I've been looking at the https://github.com/beekeeb/piantor

Particularly does the Piantor keyboard https://github.com/beekeeb/piantor supports NKRO ?

I have a piantor (https://github.com/beekeeb/piantor 2x rpi pico WeAct, halves connected by a TTRS cable, vial firmware for WeAct) keyboard built by myself (I soldered somethink like 10 years ago so I'm not an expert). It worked great but now the right half started to stop working. It happens after some idle time and happened once during usage. Diode is on on the broken half even when it does not work.

A fork of the Cantor which uses a Raspberry Pi Pico microcontroller (or other RP2040-compatible microcontroller). See its GitHub page.

Couldn't find anywhere to download keymap files for Piantor keyboard, and don't have enough determination to start from scratch designing myself. Could you please share some of your creations? Thanks. My Piantor is a RPI0 variant, if that matters.

No it is the default case, see beekeep GitHub https://github.com/beekeeb/piantor/tree/main/case

Ah yeah sorry, the piantor is not wireless (i removed the trrs cable to get them closer together). I traded off the convenience of wireless for an easier unpacking job (no need to make sure everything is charged, flip the on/off switches etc.) Not sure if someone has tried making a wireless variant. The repo is https://github.com/beekeeb/piantor

More details about this amazing keyboard you can find over here Piantor keyboard

Piantor – Pi Pico based

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.