And as always, the majority response to this will absolutely be something along the lines of “I support writers but you can fuck right off if you expect me to inconvenience myself in the slightest most superficial way in solidarity with you because actually having to modify my behavior in the simplest way is where I draw the line.”

Especially ironic considering they were horribly unreliable for long term data storage

And Apple is also pushing its own omnipresent AI.

Honestly it wouldn’t even be that hard to release full translated versions of existing programming languages. Like Python in Punjabi or Kotlin in Chinese or something (both of which already support unicode variable/class/function names). Just have a lookup table to redefine each keyword and standard library name to one in that language, it can literally just be an additional translation layer above the compiler/interpreter that converts the code to the original English version.

It’s honestly really surprising that non-English speakers have developed entirely new programming languages in their own language (unfortunately none of which are getting very widespread use even among speakers of that language), but the practice of simply translating a widely used and industry standard English programming language doesn’t seem to be much of a thing.

If I ever make my own programming language, I’m probably going to bake multi-language support into the compiler. Just supply it with a lookup table of translated terms and the code in that language.

Because it supports Unicode as variable/class/function names and Unicode includes all the characters humans have ever used, even dead languages (I assume for historians to digitize ancient texts?)

Same reason Siemens, Volkswagen, Bayer, and many more, including a ton of American ones were onboard with the Holocaust.

Genocide is good for business.

Easy solution: Switch to table UUIDs.