Just go away.

Exactly.

That –at best– gives you the same performance.

No, I’m not going to waste further time on trying to make you understand things you are not capable or interested in understanding.

Case insensitive FSs aren’t a new thing.

More precisely, they came up in a time where Unicode was not a thing.

Yes, you need to attach the locale to the filename. No, I have no idea off the top of my head of how different file systems encode or store that.

They don’t. None of them.

Or, if it is, then let’s go back to eight characters from the English alphabet in all caps. 8.3 filenames. Why not? […] Why are spaces, cyrillic, special characters and long names worth doing but case insensitivity isn’t?

Because you cannot have both.

It is either “spaces, cyrillic, special characters and long names” or case insensitivity.

What blog?

To spell it out for you, very slowly: Casing is locale-sensitive.

You cannot determine whether file A and file B have the same case without taking the language the filename was written in into account.

Which means you need to somehow attach the locale to every file (name). Your browser could implement something to add that (semi-)automatically, but if grandma is creating a file from scratch, there is only so much you can do.

I hope this helps you understand why the thing you propose is stupid.

Why do have such a strong opinion on things you –rather obviously– understand very poorly?

Why would grandma need to specifiy the locale?

Yeah, maybe figure this one out for yourself to get you on track for learning something.

someone spontaneously brings up non-latin alphabets as if they are equivalent to case sensitivity for no good reason

That sentence makes no sense. You don’t have to agree on things, but at least be coherent in your objection.

So every time grandma picks a file name she needs to specify the locale?

What a stupid hill to die on.

How would that happen?