4 ms·
Because you never want to distinguish between never and Never and NEVER and NeVer. They are all the same word. The only time that English is case-sensitive is
by lisper 8y ago
Because you never want to distinguish between never and Never and NEVER and NeVer. They are all the same word.
The only time that English is case-sensitive is when you want to distinguish between a proper noun and a similarly-spelled word, like rich and Rich. But that hardly ever matters for identifiers, which is what file names are.
- geofft 8y agoWell, I think just about all of my filenames have personal names in them - they tend to start with /home/geofft. And "never," your original claim, is not "hardly ever," your revised claim. If there are valid use cases for case-sensitive filenames, it seems like it should be allowed on robustness-principle grounds, even if they are rare, unless they impose some disproportionate cost on users of the system. And filenames don't have to be in English, and usually aren't. "geofft" is not an English word; neither is "usr" or "etc" or "tmp," let alone "xt_RATEEST.h" or "/tmp/tmp.CGZ8Lq5f". And even for common nouns in English, case matters - the UCC for instance requires certain text to be "conspicuous," and gives one example as "a heading in capitals equal to or greater in size than the surrounding text." It's pretty common for lawyers to write "conspicuous" text in all caps to satisfy this requirement. In these cases, you do want to distinguish between "never," "Never," and "NEVER".
- lisper 8y agoNothing prevents you from having file names that mix cases in a case-insensitive file system. Case-insenstitive is not the same as case-oblivious. For example: $ echo asdf > Foo $ cat foo asdf That's much less error prone that allowing you to have distinct files named foo and Foo and FOO and FoO and fOo and fOO and...
- benj111 8y agoI AGREE, CASE DOESN'T COMMUNICATE ANYTHING. .... PARDON?
- lisper 8y agoFile names aren't used for communication, they are used to identify files, i.e. they are identifiers. Case-senstivity is never the right thing for identifiers. If you find yourself needing to distinguish two identifiers that differ only by case, you're doing something wrong.
- geofft 8y agoYou keep saying "never" despite having given a counterexample two comments ago. Besides, the point of a filesystem isn't to have opinions on right or wrong. It's to store files.
- lisper 8y agoNo, I didn't. I gave a counterexample where capitalization matters in English. It does not follow that this distinction ever matters in file names. In English the sentence, "The president of the company is rich," has a fundamentally different meaning than the sentence, "The president of the company is Rich." But when naming files, or choosing identifiers of any sort, if you have two distinct identifiers whose difference hinges only on capitalization, then you've chosen your identifiers poorly. In other words, the fact that capitalization actually matters in English on occasion is a bug, not a feature.
- asveikau 8y ago> The only time that English In the comment you replied to you've just been given a critical example, and it seems like you ignored it to talk just about English. Get a Turk and an Englishman (maybe have them walk into a bar). Show them the letter I and say, "what is the lowercase of this?" They give you different answers. So what should your kernel do about open("I.txt", O_RDONLY), when the directory entry has it as "i.txt"? Tell the Turk ENOENT, and give the Englishman a file descriptor? What happens when the user changes languages and has a filename stored somewhere? I would argue it's not the right layer to solve the problem.
- lisper 8y agoThis has nothing to do with case-sensitivity. This has to do with the fact that the glyph that looks like "I" stands for different characters in different languages. That is a problem in and of itself, but the way to solve that problem is not to introduce case-sensitivity and all of its associated problems into the file system.
- geofft 8y agoWhat are the associated problems?
- lisper 8y agoAmbiguity and the likelihood of making a mistake. If you have N>1 files whose names are only distinguished by capitalization it's going to be very hard to tell which is which. Do you want thisfile or thisFile or Thisfile or ThisFile? (Now imagine being asked that question verbally.)
- geofft 8y agoShould the filesystem also ban you from having files named both "thisfile" and "thisfilе" (Cyrillic lowercase ye)? In what character sets?
- 8y ago
- scbrg 8y agoSo, this one particular language is always case insensitive, except when it isn't. Well, then... that clears it all up.