Now you know how we feel when we get US keyboards accidentally shipped over here. Biggest clue and the thing that upsets people most is the “@” key and the " key being swapped over.
I don’t know, we gave you the Beatles, Rolling Stones, Deep Purple, S.ex Pistols. Pop Art and you threw us out in 1783. To make matters worse, you gave us occasional strange keyboard layout.
Had to insert a “.” in one band’s name as it upset the forum software…
I’m likely the most strange. In 1982 while using Typing Tutor on my Commodore 64 I decided to try the Dvorak layout, liked it, and have stuck with it to this day. Advantages include being forced to remember key placement since the alteration is always in software, the keycaps don’t change from qwerty (well, an OSK does but I don’t touch type on such things so I leave them qwerty). This means I’m indifferent to keyboard backlighting—even if my fingers lose their place in the dark it doesn’t help. Disadvantages include being crippled, unable to properly type if I can’t change the layout. Like one time I had an online college course in which I had a proctored timed essay test and I had to get advance permission to change one of the computers’ layout at the testing center. Explaining what I needed and why was the hardest part—for some reason the people there didn’t even know what touch typing was much less different keyboard layouts.
Anyway, being a weirdo this way means I can’t entertain myself by throwing stones at others’ habituated keyboard preferences. :vb-surrender:
One datapoint — back when I was scheduled for a typing class in the military (and was able to type out at 80WPM when the min. was 50WPM), the instructor noted that they’d never had a Dvorak typist fail to type out on the first try.
I’d like to arrange my life so that I could switch — hopefully once I retire.
my wife OTOH uses and loves it. And she always points out that the QWERTY layout was not done to enhance usability, but is a relic from the mechanical typewriter days as a way to limit the speed so it wouldn’t break the mechanisms
BTW: For those that are wondering our understanding is that it’s touch/pen support combined with the unified memory architecture to blame. In other words there’s no way to “map the pixels” so to speak