Cries in corporate systems, balls deep in Microsoft ecosystem.

All my personal devices are running Linux however.

There’s a conlang introducing phonemic hats, so why the hell not?

This is why I dread working with anything ‘too consumer friendly’.

Wasn’t it a few years ago that scientists working on human genes renamed something because excel was chaging it every time?

Having an untraditional gTLD like .xyz makes many confused as well, especially those not in IT.

Sometimes boring is better, sticking to the fundamentals. I didn’t like when signal tried to mix crypto into it.

Isn’t Japan a well known case of chronic recession lasting for decades since the 90s? There are more general issues that other East Asian countries share like population decline.

And paywalls. Why.

Are those USB naming schemes, or edgy usernames from 2000s like xXx_31Gen3x1HardCore_xXx?

My workplace insists on using dot net classic to recreate a twenty years old VB app that should be able to drink, vote, and drive.

Please send help. SQL queries are a spaghetti mess and all the original devs are probably gone or dead.

I am so sorry, man. No one deserves this.

Then there’s the issue between scientific jargon that is different from general public use. A scientific theory has a specific definition, but it’s easy for general population to dismiss them as “just a theory”.

And this is why alcoholism is rampant. Please free me from this insanity.

I scream silently everytime.

And then there’s .net classic and .net core. Making up two entirely separate names shouldn’t be difficult for marketing executives.

I still think YYYY-MM-DD should be more apt for an international release.

I would have loved this as a drunk college kid at 2 am.

Its the same for all East Asian countries as well, but I guess slapping JAPAN on it means fast upvotes, like that "Place, Japan" meme.

For the whole continent? I thought they would try that starting with their own (proposed) regional block, the Eastern African Federation.

So this is why we’ve been seeing rows of “Login with $SpecificProvider” instead of a universal format using username@provider as we all hoped?

If we’re being really pedantic, the last part in Korean is counted with different units:

• 각 as precomposed character: 1자 (unit ja for CJK characters)
• 각 (ㄱㅏㄱ) as decomposable components: 3자모 (unit jamo for Hangul components)

So we could have separate implementations of length() where we count such cases with different criteria… But I wouldn’t expect non-speakers of Korean know all of this.

Plus, what about Chinese characters? Are we supposed to count 人 as one but 仁 as one (character) or two (radicals)? It gets only more complicated.

Hope the indexed instances don’t get taken down years down the road, or have some sort of independent archive to consult later.