So I started to actually create my own. And I want it to be programmable. And movable, as in you can move the key around, enlarge or shrink them. And when I say I want them programmable I meant to pull a little gizmo out of it, hook it up to a separate power source and load preset or connect to computer and use an app to make the keys look different.
So far my idea is to have each key include a magnet, an ESP32 chip and a small LED screen on top of it. The controller to all those 110+ ESP32 chips will be a RPi CM4 module, which will also be the USB connection for the PC. That's one iteration because this way I can actually have a click-clack mechanical one. The other iteration is to just have a big ass touch screen and the RPI underneath to just play that as an app that simulates the keyboard. Prettier, way more customizable as key positions/size go but no click-clack sound/feeling.
I'm $2000 in my research hole for this with nothing to show up for but is fun. Probably next year I'll finish it :)
However, I would love to have your software-defined visually configurable keyboard as a second one on my table and every app using it as a sorg of a "toolbar" / command palette. This was what Apple tried sort of (it would have been nice idea if they didn't sacrifice a real keys row for it). To me it sounds like an additional display with touch support can do the job.
The thing I like the most about it is that I don't have to manually install and managed various tool chains and it's a lot more flexible than the Arduino ide.
The "keep hands on home row" is the motivation behind omitting the "unnecessary" keys, at least for the keyboards which use a small spacebar and give the thumbs more keys to use.
With those small 36-key keyboards, your hands pretty much have nowhere to go except to remain on home row.
> as many keys as possible
I once saw someone made a keyboard with 450 keys. https://relivesight.com/projects/433/
I switched to a OLKB Preonic over a year ago and haven't looked back.
After you get used to the smaller factor and non staggered keys format you realize how ridiculously and unnecessarily huge and clunky traditional keyboards are, even laptop keyboards.
It's like traveling with a 65 liters bag for years before you learn you can just carry a 40L and travel with less crap and much lighter.
It took me a couple of months to come up with the layout that worked for me (and even today I still optimizing it), but once I figured it out the typing experience became just such much better.
The QMK configuration tool makes the process of configuring the layout painless and super quick, so you just need the patience to try and iterate.
In ~2000 I started suffering from tendonitis and my coding job became very painful, I tried kind of the 'easy onramp' ergo options at the time, namely the ms 'natural'. It did not help. Eventually someone pointed me at the kinesis advantage (then essential) and I bought one. After some struggle coming to terms with thumb keys and wells and ortholinerness I switched to it for all tasks except for gaming and my symptoms basically disapeared.
About 10 years back I was in a job that was potentially going to cause me to travel a lot, at that point I had already modded my kinesis advange keyboards with custom controllers and wanted to try and build something that travelled better, was smaller, while still not fucking up my wrists.
I built a lot of keyboards trying to shrink my luggage. I went ortho and built a split preonic, uncomfortable, then I went down the road that leads to corne/iris/etc (thumb keys, vertically aligned but not horizontally aligned). More comfortable but the thing i always ran into when removing keys. Overhead, you have to remember what layer and key you put xyz rarely used symbol on (and when you are a software engineer that's a lot of the symbols).. at the end of the road I built a very low profile board based on the dactyl with the same number of keys as the kinesis advantage minus the f-key chicklets. Reducing the number of layers i have to remember to 1 that only contains the grave and the fkeys.
Then covid hit and I didn't have to travel anywhere. I take my dactyl when I go see my parents, and unloaded most of my other boards for cheap. (i kept a 65 that I play games with)
Right.
The benefits of reducing hand travel / stretching come at the cost of additional complexity. Not everyone will be comfortable with that complexity.
I find the complexity acceptable; and in many ways more coherent than traditional layouts. e.g. I'd keep slash and backslash (/\) adjacent (or otherwise paired); a question mark (?) is frequent enough even in prose; so, pipe (|) remains paired to backslash. -- But, yeah, it can be annoying for keys which are used very infrequently.
I ended up getting the keychron v6, it's wired but fine. Their wireless keyboards are apparently a bit buggy, not sure if the new ones still are.
QMK is an absolute treasure. You can use your web UI to setup custom keymaps and stuff using the chrome USB feature. But I may have went off the rails, as it's pretty simple to completely customise your keyboard with layers etc if you know a bit of C.
Warning; this is a gateway into a land of a obsession. :-)
What I've seen happen though is that especially on linux you need two-modifier combos (ctrl-shift/ctrl-alt) to perform what you could have done with a single Fn keystroke. Or burn a few extra keys and increase complexity with layers. I went this route a decade ago, and I'm not a fan personally. Removing the Fn row saves 2cm of vertical space from your desk. I see it as completely pointless, even if you never use the Fn keys.
And I don't buy the "reduced finger travel" argument either. Holding the modifiers in weird positions to access an extra layer is usually worse than a more spacious keyboard where your hands can be kept further apart and require less chording.
But yeah... I commented on another thread on keyboards, and the current keyboard craze is mostly about customization and looks, and very little about the actual typing experience IMHO (there are exceptions of course..).
The number pad is another example of this. Typing numbers is massively more comfortable (and quicker too) on the number pad than it is with the row of numbers just below the F-keys.
The amount of desk space people save is so negligible, particularly when people who buy these keyboards typically work in “paperless” offices, that I never understood the appeal.
I guess it boils down to people wanting their keyboards to look pretty rather than being actually useful.
I agree entering numbers is better on a keypad though.
Plus I’ve been using keyboards longer than a lot of (probably most) developers on here have been alive and I haven’t ever found using the number pad to be even remotely an effort.
And all the digits are right there, not at some opposite ends, e.g., UIO789 JKL456 M,.123 on a qwerty
Ultimately there’s going to be a lot of personal habit baked into these preferences and we are talking about micro-optimisations at best anyway. Which I why I think it’s probably better to just agree to disagree.
And the mistake in your first response with the numbers on the opposite ends isn't about "personal habit"
The ironic thing is this conversation of ours would have cost us more energy than what would have been saved from a lifetime of any of your keyboard optimisations. Which is why I roll my eyes when people try to intellectualise their keyboard preferences as some kind of revolutionary time and effort saver.
There are (roughly) two families of "smaller keyboards".
Those with a big spacebar, and those with multiple thumbkeys.
Big-spacebar-small-keyboards are like laptop keyboards.
Whereas, for other kinds of small keyboards (such as the moonlander or planck) which provide thumbkeys, I'd say the emphasis is more about "bringing the full functionality of the keyboard to within easy reach of the hands" rather than "remove keys for whatever reason".
On traditional keyboards, the thumbs only get to use 1 key. A big spacebar is such an odd and inefficient use of keyboard real estate.
Whereas, with 2-3 keys each, the thumbs can be put to good use. e.g. It's much more comfortable to press backspace with the thumb, than to move your hand (or reach with the pinky finger).
Let alone than with the row of numbers holding a Shift pressed (some languages require this because they remap the row for extra letters).
e.g. At home, I only very occasionally enter numbers. I very frequently use my mouse, and have large monitors. So I sacrifice slightly less convenient number entry for slightly more room for my mouse(pad) all the time.
At work, I have a full-size keyboard and I spend a higher proportion of my time typing and entering numbers.
I rarely type numbers and find that the "top row" number keys are adequate for when I need to.
People don't need a keypad because they have the digits row. But there are languages (in Europe) which reuse the digits row for extra letters (which don't even fit there) so you have to press shift to enter a digit (yes, you can't enter such a letter in capital without using CapsLock), unless you have a kaypad.
People don't need F-keys (so these can be reused for multimedia controls) because they are not techies. Insert for the same reason.
People don't use Delete/Home/End/PgUp/PgDn because they are completely uneducated about the basics of using a computer and use mouse/touchpad, arrows and backspace instead. Believe it or not, I've met people who don't even know Ctrl+C/V (let alone Ctrl+X or Ctrl+Z) and would always use the right-click menu (which even requires an additional keyboard key to be held pressed on a Mac) to copy/paste anything.
This said, compact keyboards target anglophone non-techie users (or hardcore VIM fans who have ways to do everything without leaving the home row).
The languages appears to be Czech/Slovak. It would be more useful to mention this, than to repeat the basic point in four or five comments.
What's weird about home row or thumb mods?
Lol right. And I add a shift layer to the fn row as well, to add more fn keys. Sadly a lot of apps won’t support fn20+ but u find more utility binding them to hand crafted actions anyway
I started out with a moonlander, which had a lot of keys (36 each hand) but to be honest, I'm trying to minimise as much as possible, and remove keys from it. That way I'm fully constrained to the home row.
Also, layers are amazing and sounds like something you might want to look into. Hold 'a' and use hjkl for media keys, etc. It's all very flexible
I was just discussing this yesterday with a friend. It's funny how rare and technical it is to understand layers when everyone uses layers every day - shift + 3 does not render 3, but #. But we don't talk about it that way.