I’ve used a US-QWERTY keyboard layout my entire life. I’ve seen other layouts that do things like reduce the size of the enter/backspace keys, move the pipe operator (|) and can’t wrap my head around how I would code on those.
What are your experiences? Are there any layouts that you prefer for coding over US English? Are there any symbols that you have a hard time reaching ($ for example)?
Always used it. You have instant semicolon instead of Ä, which you don’t use when coding, and brackets and curlies are a breeze, the comfort is well worth it
Also, it’s even ISO standardized, so yeah, it’s an international norm.
Pragmatically: most programming languages are developed in a way to that it’s easy to type them up on a standard us layout. As English only has 26 letters, which is less than any other language using the latin alphabet (don’t even start me on languages with accents like ñ or that differentiate between à, a, á, and â), all the special characters are usually easily accessible. Most others layouts will tuck them away behind non-trivial combinations in favor of improving accessibility of extra letters and special characters. Cuz essentially in human language you barely need * and [. So, I guess, right ctrl + left shift + 9 will do? how do you feel about coding in python on that. Or on a keyboard where the space for your | has been allocated to some letter ø and your OR operator has been moved to the numpad.
Could just as well have been a writing prompt community. It’s just writing ANSI characters for the most part.
Also, it’s even ISO standardized, so yeah, it’s an international norm.
I’d wish something being ISO meant it’s the norm, but that’s just not the case. #ISO8601Gang
Pragmatically: most programming languages are developed in a way to that it’s easy to type them up on a standard us layout. As English only has 26 letters, which is less than any other language using the latin alphabet (don’t even start me on languages with accents like ñ or that differentiate between à, a, á, and â), all the special characters are usually easily accessible. Most others layouts will tuck them away behind non-trivial combinations in favor of improving accessibility of extra letters and special characters. Cuz essentially in human language you barely need * and [. So, I guess, right ctrl + left shift + 9 will do? how do you feel about coding in python on that. Or on a keyboard where the space for your | has been allocated to some letter ø and your OR operator has been moved to the numpad.
As a user of a keyboard layout with æ, ø, å, who also uses python daily, I can promise you that there are zero issues with it.
Most people will grow up with a keyboard layout designed for their native language’s need. If it uses Latin characters, there should be minimal issues using it for programming too.
I just explained what the issues are. Programming languages heavily rely on special symbols.
If you haven’t watched yourself from the outside, how do you know “there are zero issues with it”? You might be constantly breaking the typing flow and need to use a two-hand combo for some mundane []. While someone on a US layout never needs to lift their hands of the keys, because all they need is a ctrl with a pinky + right hand within reach.
When I learn a new language, I also learn a keyboard layout for it. Or do you also write in Spanish on your keyboard? How do you make an à and an á?
Ah, that’s right, you speak two languages, you’re stuck using your comfort zone layout, and you’d ofc argue “zero issues”.
If you haven’t watched yourself from the outside, how do you know “there are zero issues with it”? You might be constantly breaking the typing flow and need to use a two-hand combo for some mundane [].
Because I don’t have the issue you’re projecting. And if someone do have that issue, what type of programmer (assuming no physical disabilities) has their productivity limited by their typing speed? No one would be my guess.
While someone on a US layout never needs to lift their hands of the keys, because all they need is a ctrl with a pinky + right hand within reach.
Cool, same here , just that sometimes we press alt gr instead of ctrl.
When I learn a new language, I also learn a keyboard layout for it. Or do you also write in Spanish on your keyboard? How do you make an à and an á?
ctrl + \ and then a for à and alt gr + \ then a for á. It’s really not much of a hurdle. And definitely faster than trying to learn a new keyboard layout that I can’t type on without looking.
Ah, that’s right, you speak two languages, you’re stuck using your comfort zone layout, and you’d ofc argue “zero issues”.
Are we talking actual languages or programming languages? Either case, you assumption is wrong. I don’t understand where all your antagonistic energy is coming from. It’s just a keyboard layout, there isn’t a single correct one. Just use what you’re used to and that you can write with a good flow, which for most people will be the layout they grew up with and can type in the blind with.
Not only are there other ones that are also ISO standards when it comes to software layouts, but funny enough, when it comes to physical layouts, US keyboards normally follow an ANSI standard (not an ISO one), whereas many non-US keyboards typically follow a physical key layout known as "ISO Keyboard", so one could argue those are more of an "ISO" standard.
No keyboard layout uses ctrl like that..... in fact, I don't think you ever really need to press more than one modifier in any standard non-US keyboard. Unless you have a very advanced custom layout with fancy extra glyphs... but definitelly not for the typical programming symbols.
ISO keyboards actually have one more key and one more modifier ("AltGr", which is different from "Alt") than the ANSI keyboards.
In fact, depending on the symbol it might be easier in some cases. No need to press "shift" or anything for a # or a + in a German QWERTZ keyboard, unlike in the US one. Though of course for some other ones (like = or \) you might need to press 1 modifier.. but never more than 1, so it isn't any harder than doing a ) or a _ in the US layout.
Same effort as getting &* and () on a US layout (so, modifier key + 7 8 9 0, respectively), the difference is you press AltGr instead of Shift as the modifier. And i'd argue its actually easier to press AltGr with the thumb than shift with the pinky.
There’s lots of programmers on languages that need more keys readily than us keyboard has. Äöüß, just to give an example.
I don’t know, every time I read a post like this I’m kinda speechless. I know lots of Americans and many of them are brillant and open-minded, but then there are posts like this which are completely oblivious that there are reasons for other keyboard layouts.
The reason OP can’t fathom programming on those is that they aren’t used to it. If you grew up with non-us layouts you similarly couldn’t fathom programming on the us layout.
Sometimes I feel like people refuse to even think about acknowledging that there are other experiences than their own. Go out, try out new things, exercise your brain and callenge yourself.
I’m not American, I speak a few European languages, I can type on a multitude of layouts. They all suck for programming, I know firsr-hand. And watching those people who “grew up with a layout” to use two hands for a ctrl+z is both hilarious and painful.
Wtf, who needs two hands for that? Do they have children’s hands?
It’s all a matter of habit - for me all layouts but my native sucks for anything to do on a keyboard. The only thing that sucks is if keybinds are set to shift-/ because / is already shift-7. I haven’t found a replacement for that yet. Forgot which program used that and for what, but I remember it was a bummer. Still wouldn’t spend all that time and energy and slowdown learning a different layout.
Not culturally dense, but absolutely unwilling to consider cultures outside their bubble other than as mere curiosities for entertainment. I stand by that.
Not unable to learn a new layout, but unwilling, because I don’t see the point. Why would I waste time and energy on something that will at most bring me one more shortcut to use? Programming is not about typing speed. If the bottleneck for you is typing speed, your job is very different than anything I’ve seen or heard of.
I have never seen anyone but my computer-illiterate mom use two fingers for ctrl-z, hence I was expressing my bewilderment about that. I’ll probably be able to do that move blind with one hand, and so are all of the people I know who use the computer in a professional setting. The only explanation I had for that was that they have exceptionally small hands so it’s a necessity. If you want to take that as an insult of your hands, be my guest, but I’m done here.
I used to use the Brazilian ABNT-2 layout, it’s pretty much just a US layout with accent keys that activate like a second layer for some specific keys to display specific Portuguese language characters such as ç á à â ã é è etc. It’s surprisingly ok for programming as it doesn’t get in the way because you have special keys to activate the 2nd layer and most of them you need to spread shift + something in order to activate them. I’d say it’s a good layout.
I’m Czech and also speak fluent German, but I rarely use my native languages on my personal PC, so I got used to the US layout. Nowadays I use US layouts that have my native letters on the AltGr key, my Linux pc has an “American - Czech, Slovak, German” layout like that and at work on windows I use the Czech Programmer layout. However, most of my coworkers use the regular Czech keyboard, even for programing, which freaks me out.
It depends on what you’re used to and the programming languages you use. I learned typing on a German QWERTZ keyboard and while that works for languages like Python and Haskell, which are indentation-based, but for languages which use braces like Java, C, Rust, or similar, it can be annoying to have to use altgr+7 or altgr+0 for { and }. Thus I switched to a US ANSI layout, which was nicer for those specific characters, but caused problems when typing local characters like öäüß. After switching to Linux I set up a compose key, letting me press compose + a + " for ä for example, and while that’s a decent patch, that still breaks the typing flow. So now I’m in my ergo keyboard phase and trying to get my own personal layout going, which meets my own needs for needed characters, based on a colemak-dh design.
I used to use ANSI, but then moved to England and bought a laptop and returned it because of the “weird” ISO keyboard, then forever bought dell because I could customise it.
Moved back to ANSIland, but will still probably just buy dell.
I use Spanish QWERTY layout and it’s… weird for coding.
I’m used to it from my whole life so that’s what I use but sometimes brackets or special symbols are weird.
I’ve always wanted to change to use US-International layout. So I can keep ñ and áéíóú, and also have easy access to coding symbols. But I have never got around it.
Anyhow I still think that whoever designed ISO layouts messed up. We should use US international layout. That’s my two cents.
On UK keyboards the £ replaces the $ and $ replaces ’
Double quotation marks " are in the same place though so a lot of british programmers don’t use single quotation marks because they are hard to press. If your touch typing you have to reach all the way to the bottom right with your right hand little finger and it’s just not worth it.
I use Colemak where most punctuation is at the same place as in the US English layout, which programming languages seem to be optimized toward. For the layout I prefer ISO for the larger Enter key.
I use US-QWERTY but with the pipe/backslash key as backspace, and the key where backspace usually is gets turned into two keys, pipe/backslash and grave (yes, there is a keycode for grave (`) by itself).
I use a country-specific ISO layout, and while I’m very aware that certain things are insanely awkward compared to a US keyboard, like { }, [ ], $ and /, you get used to it. You get used to everything over time. I even use the default vim bindings and have gotten used to them as well.
I prefer ISO layouts. ANSI somehow just seem inefficient to use. I habe layers for CODI g so I have my brackets/braces on the hometown along with other relevant keys. Long live custom keyboards
Add comment