[bsnnkv]

I have quite a few of these sorts of keyboards, including the Ergodox EZ. I think for generalist usage they can be adapted to pretty easily, but as a developer, the lack of dedicated keys for [, ] and ' is an insurmountable obstacle for me.

Those keys are in my opinion perfectly placed on regular keyboards and no amount of layering, tap dancing or anything else will ever come close. Please somebody just make a split ergo keyboard where the right side has extra keys for regular programming symbols on the top layer. The two halves do not need to be symmetrical.

[mkozlows]

I think this is honestly just a thing to get used to. I use the semi-colon/quote keys for [] and p/backslash for {}. It means I need to hit a modifier key to hit them, but you always had to hit a modifier key (aka shift) to hit curly brace anyway, so this really isn't a big deal.

With QMK, "layers" aren't this whole giant huge deal. It's like hitting the shift key, except just a different physical key, probably by your thumb.

[tevon]

Yea I hear this, I moved my ` and | symbols on my dygma raise, an mostly got ride of \ (its on a different layer), since I was only really using it for \n.

The biggest change for me on the Dygma raise was the thumb cluster. I moved my backspace to my thumb, as well as different layer shifting keys. The muscle memory is quite easy to learn, since your brain is already "expecting" to use your thumb to shift to other functionality (since we use our thumb to press command), so it simply makes all my vscode shortcuts 2 simple strokes instead of 3 or more.

Also moved my arrow keys under my fingers on a different layer, makes it so you don't need to move your hands when navigating around code. On that same layer I added option + arrows as well for fast navigation.

[krzyk]

and lack of F1-F12 is a show stopper for me, I use them in my IDE.

[rgoulter]

These small keyboards trade-off the benefit of "bring all the keys within easy reach of the hands" at the cost of a more complicated layout.

The intent is "be able to press F1-F12 without having to move hands so far from home row"; it's not "I want a smaller keyboard and don't need F1-F12".

[hwbehrens]

I've been using these types of keyboards for a couple years now, and I find that although the enthusiast community has sort of gravitated towards <50 key layouts, trying to achieve the complex combinations often required by IDEs can be an exercise in dexterity (both physically and mentally).

For example, let's say you need to do Shift-Option-F12. First, you need to hold a modifier to bring your F key layer, possibly a separate or chorded modifier to get you to the F-keys above 10 since you only have have 10 numeric digits. Then, that needs to be compatible with both your shift modifier AND your option modifier, which with only 2 thumb keys per side it probably won't be. So, then you think, oh no worries, I'll just set up a single shortcut that does what I need, but then you end up with a profusion of shortcuts that you need to remember.

I've found that in practice, I can't really go much below 58 keys and 3 layers without requiring tap-and-hold or losing some of my less-frequently used chars (` comes to mind), so I can sympathize with the ancestor posts.

[lucw]

Why would you ever need to hit Shift-Option-F12 ? They keyboard is customizable and the IDE shortcuts are customizable. I have a VsCode layer on my crkbd (https://github.com/luc-languagetools/qmk-crkbd-vscode-builde...). I generate the actual keycodes using this python script, which also outputs my VsCode keybindings.json: https://github.com/luc-languagetools/qmk-crkbd-vscode-builde...

[rgoulter]

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.

[lbussell]

I picked up the Miryoku layout a year or two ago and the home row mods (Ctrl, alt, shift...) make all the difference. Adding a thumb key into the shortcut to hit a key on a layer doesn't take much extra mental energy and it becomes muscle memory for certain shortcuts. It's a little like playing different chords on the piano. I added some customization for Vim arrow keys and now I don't think I'll ever go back.

[mkozlows]

"a profusion of shortcuts that you need to remember" -- sure, true, but you're already talking about something esoteric like shift-option-F12. Were you remembering that in the first place?

[strongly-typed]

I hate to be that guy but this line of reasoning leads to “redefine every shortcut for every app” in order to fit your keyboard. Yes, it’s possible, but cognitive overload is also a thing.

[eviks]

you wouldn't use horizontal numbers, but a numpad-like layer, so that'd be just one extra f layer tap / hold

[strongly-typed]

While I agree in theory, in practice I feel like there is a noticeable difference between the frequency of F1-12 and the punctuation characters OP listed. Moreover, there are not many tools to help people find layer arrangements that are actually ergonomic besides their own intuition. Layers are surprisingly complex and subtle for many reasons here are a few I can think of:

- Layer transition fatigue: If you have many layers, it can be difficult to remember which key(s) triggers them. This can be improved with time and practice. In addition, you might want to arrange the symbols on your layers to minimize the amount of layer transitions needed. For example, if you type ./ a lot if would be nice if they were on the same layer and either a roll or an alternation.

- Awkward finger patterns: if we go back to the ./ example, if for some reason you decide / must go on another layer, then you probably want / to be close to period. If you design your layer in a way where / ends up under qwerty P, then you’ll have to contort your fingers to make the ./ pattern. This gets way more complicated when you consider all the possible symbol patterns such as ->, =>, :=, </, ./, [i], [j], |>, (“, “), ):, etc…

- Unexpected layer transition same finger usage: people will sometimes naively put layer transition keys in suboptimal places. For instance, if you use right thumb for space, then I would argue it’s a bad idea to use another right thumb key for shift. The reason is because in between sentences you put a space after the previous sentence and then press shift to capitalize the next letter. If they space and shift are on the same finger then you will probably find this sequence uncomfortable. A similar logic applies for backspace. I would argue space and backspace should be on the same thumb because they are pretty much mutually exclusive. Also your space thumb is used to repeating, and backspacing often involves a lot of repeating.

Overall, I think layers do have a lot of potential to work, but I feel like there aren’t many tools to help people iron out all these subtle issues. I’ve been working on making such a tool, but testing it takes a lot of time due to the first point.

[uticus]

Exactly this. I would add also, do you want to accomplish by additional hand/wrist movement (access F-key row) or by additional keypresses (layer, tap-dance, etc)?

[chaxor]

What on earth are you talking about?

Of course it has F1-12, it's just in a better place. It's completely programmable, so you can choose something that makes sense to you.

[krzyk]

Well, I'm looking at that keyboard and don't see F1 for example, so there is no such key.

Using key combination for basic keys is like using mouse to emulate keyboard.

[chaxor]

Ah, yes I know so many devs that struggle to type G. Shift+g is so hard these days.

[krzyk]

I suggest you read https://news.ycombinator.com/newsguidelines.html section about comments.

If my IDE requires me pushing SHIFT + F3, I would need now to push SHIFT+ALT+F3? How is that in any way more ergonomic? I assume split keyboards are the golden standard of ergonomic design (or I thought they should be).

[ajford]

I thought this was going to be a barrier for me as well, but after using a Moonlander (one of ZSA's other keyboards) for over a year now, it's not as bad. I have a layer that has F1-10 in place of 1-0, then F11 and F12 are on overflow keys.

I've found that the hotkeys I most frequently use I moved in to more convenient hotkeys/macros (for example code folding/unfolding to three common levels, debugger stepping), while others just stayed where they were.

I would say that you'd probably want to try a larger keyboard than the Voyager though if that's a concern though. I'm reticent to try such a smaller keyboard, and I found the ~70 keys of the Moonlander to be more inline with what I like.

[mkozlows]

Modifier key plus the number row gets you that trivially, and it's no different from having to hit Fn + F-key on a laptop. But even better is that if there are things you use regularly, you can map them up to a more convenient place.

[krzyk]

I don't use Fn on laptops, that's backwards. F1-F12 have basic functionality, when I want to play around with something less common (like changing volume, brightness) I use Fn + F key.

[Zambyte]

https://configure.zsa.io/voyager/layouts/default/latest/1

[tevon]

Same I use them constantly, but just set one of your thumb keys to shift to your functions row. You can map all the way up to F24 then! and have any other IDE specific commands in that layer as well.

I use F all over the place in VS-code and have them all mapped on my dygma raise.

[lucw]

I agree. On my ergodox, the top row was f1-f12, and I had a virtual numpad on a layer.

[mdavidn]

The Kinesis keyboards keep those keys. I've been using a 360, and the lack of function keys has bothered me less than anticipated.

... I use IDEs from JetBrains, a company that seems to view muscle memory for crazy keyboard shortcuts as a moat.

[lucw]

I don't get it, you can make a [ , ] key anywhere. The ] key could be to the right of your pinky on the homerow. The [ key could be the one right above that. Personally, I have ()[]{} on the home row, activated by a layer and i'm never going back.

[tiltowait]

YMMV, but I think the Keyboardio Model 01/100 has a pretty great layout for programming. The keys are in a different spot, but they're easily reachable, and the palm layer toggles mean you don't have to contort at all to hit them.

[anotherevan]

I recently got a Keyboardio 100 but am really finding it hard to adapt to, in large part because too many symbol keys are moved around, making it a pain for programming in particular.

More details on this comment: https://news.ycombinator.com/item?id=37398872

[uncletaco]

I always swap out the semicolon for the apostrophe because I honestly don’t think that key gets enough play to have its position on the home row.

[mixmastamyk]

Nice. Python programmers now want to move semi to the shift state (and colon without) for a while as well. ;-)

[drekipus]

I moved colon to under "g" on layer one (which I hold with my thumb) and it's surprisingly effective,

Same with # under a, and all of the brackets under erdfcv keys