ministryofwarp

You sound like a helpful world citizen. The other problem the US has is that it is illegal for a US Citizen to pay a bribe but there's no realistic enforcement. Luckily you can help solve this. Whenever and wherever you travel you can keep some forms with you and every time you are pulled over you can fill them out with the police in quadruplicate so that each of you can mail them to Washington. At some later point the US can try to cross reference and determine who didn't mail theirs and then whether anyone was actually under US jurisdiction during the incident.

If you haven't broken the law, why would you be willing to come down to the jail and breakfast in a cell each morning?

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.

Helix OTOH looks good.

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.

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.)

Its about the Gulf of America. Arguments persist about its Easternmost boundary but in the west it extends from Baja California to British Columbia.

It reemphasizes the question of importance. Would a user accept their data needing a AI implementation of a ("manual") migration and their flow completely changing? Does reliability to existing users even matter in the companies plans?

If it isn't a product that needs to solve problems reliably over time then it was kind of silly to use a DBA that cost twice the Backend engineer and only handled the data niche. We progressed from there or regressed from there depending on why we are developing software.

People love to point out a hypocrite but math and statistics are rarely kind to laws that always hold true.