I'm puzzled by the idea that positional constant
is good for key bindings. How does the machine I
ssh to know my keyboard layout or whether I am
using a input with a related positional concept?
(I suppose I should say I was puzzled by it, and
now I am puzzled why this idea is back yet again.)
> How does the machine I ssh to know my keyboard layout
Why does it need to? If you are using say, Dvorak, you can just pick the keyboard layout by pressing `*` (a keybinding which is not affected by the chosen keyboard layout)
The machines and coworkers I have have no idea what I am using
locally if they don't watch my typing, it could be QWERTZ or
Turkish-F it could be a chorded keyboard.
Going backwards to layout makes no sense to me. They then can't
tell me what to type, we get to fight about env defaults, etc..
And for what? If your composition is any good it is approaching
the abstract of code so looking at your hands and some visual
feedback is of little value as it traverses the whole context.
It's good at least in my case because I switch between Dvorak (Corne) and Qwerty (laptop's keyboard) all the time, without positional keymap, I would have to develop two sets of muscle memory
The effective freedom to choose keyboards like Dvorak relates directly
to the privacy of a remote vi not breaking the privacy layer of this
abstraction. Do what we do because the servers won't be updated or
we will specifically lock their choices, etc..
After a few years of trying to get along directly in local
pair programming or similar with people with local largely
insane keymaps I decided to make use of fences and privacy
making good neighbors and I don't want those fences ruined.
Even without my intended uses for this abstraction, positional
habits is the first step of getting people out of the crib,
a crib is easy to sell a start in but not a place to retire.
