back
1 comments
I would recommend Torvalds on this: https://lwn.net/ml/linux-fsdevel/CAHk-=wg2JvjXfdZ8K5Tv3vm6+b...

As for my own thoughts on top...

In US-ASCII, case insensitivity is easy. Outside of that, your operating system kernel has to have opinions on "Ö" being the upper-case "ö" and so on. But why stop there? Should "Ö" be considered the same thing as "O"? How about Ø? Or O with diaeresis[1], which looks exactly the same as "Ö" but is in fact a different character? How about Cyrillic O vs Latin O?

But that also means that your kernel now has to have opinions about filename encoding. Maybe someone will come up with an idea so obviously superior to UTF-8 that it'll supersede it just as UTF-8 ate everything else, or maybe nobody will. What I am glad about, is that filename encoding wasn't baked into Unix in the 1970s, or indeed at any time prior to about 1993.

So, your operating system needs knowledge of all of Unicode and to care about filename encoding for...what gain? It's only weird if your previous experiences with operating systems tell you that it is weird, and calling it weird is not the same thing as being an actual usability problem.

In fact, as witnessed by the fact we're capitalising the first letters of our sentences in our comments, I would argue that case sensitivity is the default in normal writing (the word "it" being a fine example; if I had said "IT" you would have read the sentence differently), and so if anything's weird and counter-intuitive it's treating case as irrelevant.

[1] https://en.wikipedia.org/wiki/O_with_diaeresis_(Cyrillic)

Such a long comment and again what's your use case exactly?

When do you need files e.g. named O.txt and o.txt in the same directory? Won't you yourself be confused by them? It's the simplest example and it already shows that case sensitive file systems bring nothing but confusion.

I don't have a use case. I am saying that it requires zero effort to treat filenames as a big bag of bytes containing whatever, encoded however anyone wants them to be.

Anyone arguing for case-insensitivity has to both a) demonstrate that this is a source of confusion in the real world, by actual people using computers in UIs that exist today, rather than "when I think about it that's kind of weird because it doesn't behave like Windows" or hypothetical oh-dot-texts and b) come up with a better plan that handles the world outside of US ASCII.