News for hackers. Stuff that matters.
Re:Things you wish you didn't need to know about S3 by pavlov on Friday May 31, 2024 @01:26AM (#40531789)
Case insensitive is how humans think about names. “John” and “New York” are the same identifiers as “john” and “new york”. It would be pretty weird if someone insisted that their passport is invalid because the name is printed in all caps and that’s not their preferred spelling.

IMO the best thing would be to call Unix-style case-sensitive file names something else. But it’s obviously too late for that.

Re:Things you wish you didn't need to know about S3 by lalaithion on Friday May 31, 2024 @02:54AM (#40532179)
The word “Turkey” is not the same as “turkey”, “August” is not the same as “august”, and “Muse” is not the same as “muse”. https://en.m.wikipedia.org/wiki/Capitonym
Re:Things you wish you didn't need to know about S3 by pavlov on Friday May 31, 2024 @03:32AM (#40532370)
Yet "TURKEY" is not a separate word from "Turkey" and "turkey". Ultimately context disambiguates these words, not capitalization.
Re:Things you wish you didn't need to know about S3 by justincormack on Friday May 31, 2024 @05:01AM (#40532818)
And “polish” and “Polish” are not even pronounced the same.
Re:Things you wish you didn't need to know about S3 by scosman on Friday May 31, 2024 @07:59AM (#40533958)
They might be at the beginning of a sentence (depends on the reason for capitalization).

It’s more like identifier reuse, on a case insensitive “system”.

“John” isn’t the same as “John” if I’m talking about two separate Johns.

Re:Things you wish you didn't need to know about S3 by bigstrat2003 on Friday May 31, 2024 @02:47AM (#40532152)
Agreed. I think case sensitivity in Unix filesystems is actually a pretty poor design decision. It prioritizes what is convenient for the computer (easy to compare file paths) over what makes sense for the user (treating file paths the same way human intuition does).
Re:Things you wish you didn't need to know about S3 by JackSlateur on Friday May 31, 2024 @07:11AM (#40533553)
But end users do not speak to filesystems.

Programs speak to filesystems.

Re:Things you wish you didn't need to know about S3 by howerj on Friday May 31, 2024 @08:54AM (#40534529)
Except that is not true, it is sometimes convenient, and sometimes very inconvenient and not wanted. My reasoning for file systems that are case sensitive is the following:

1. Some people want file systems to case sensitive. 2. Case sensitive is easier to implement. This is very much not a trivial thing. Case insensitivity only really makes sense for ASCII.

In the camp of wanting case insensitivity:

1. Some people want file systems to be case insensitive.

There is more in favor of case sensitivity.

Re:Things you wish you didn't need to know about S3 by kaashif on Friday May 31, 2024 @09:11AM (#40534717)
I don't know if that's right. The most obvious way two characters can be the same is if they actually look exactly the same i.e. are homoglyphs https://en.wikipedia.org/wiki/Homoglyph

But no filesystem I am aware of is actually homoglyph insensitive.

Case insensitive filesystems picked one arbitrary form of intuition (and not even the .oat obvious one) in one language (English) and baked that into the OS at a somewhat deep level.

You say "human intuition" - are those using different writing systems nonhuman then?

Re:Things you wish you didn't need to know about S3 by sham1 on Friday May 31, 2024 @10:02AM (#40535299)
But the thing is that the file system doesn't need to be case-insensitive for your system to support human intuition! As others have said, people don't look at and use filesystems, they use programs that interface with the filesystem. You can absolutely have a case-sensitive system that nonetheless lets you search files in a case-insensitive manner, for example. After all, to make searches efficient, you might want to index your file structure, and while doing that, you might as well also have a normalised file name within the index you search against.

Now, as you said, UNIX did the choice that's easier for computers. And for computers, case-insensitive filesystems would be worse. There are things that are definitely strange about UNIX filesystems (who doesn't love linefeeds in file names!?), but case-sensitivity is not one of them.

Re:Things you wish you didn't need to know about S3 by 7bit on Friday May 31, 2024 @12:03PM (#40536820)
In Germany there is a lowercase letter ß. It actually is a ligature of the letters s and z. It does not have an uppercase variant, because there is no word that begins with it. One word would be Straße. If you write that all in uppercase, it technically becomes STRASZE, although you almost always see STRASSE. But if you write that all in lowercase without substituting SS with ß, you are making a mistake. And although Switzerland is a german-speaking country, they have different spelling and rarely use ß -- if not ever.

This is just one of many cases, where case-insensitiy would give more trouble than it's worth. And others pointed out similar cases with the Turkish language in this post.

Re:Things you wish you didn't need to know about S3 by Hamuko on Friday May 31, 2024 @02:41AM (#40532112)
Humans will also treat "Jyväskylä", "Jyvaskyla" and "Jyvaeskylae" as the same identifiers but I don't think that's a good basis for file storage to have those be the same filenames.
Re:Things you wish you didn't need to know about S3 by pavlov on Friday May 31, 2024 @03:34AM (#40532380)
In the era of Unicode, this battle is pretty much lost. Several different code point sequences can produce the glyph 'ä', and user input can contain any of these. You need to normalize anyway.
Re:Things you wish you didn't need to know about S3 by glandium on Friday May 31, 2024 @06:38AM (#40533361)
And macOS does that normalization at the filesystem level.
Re:Things you wish you didn't need to know about S3 by justincormack on Friday May 31, 2024 @05:02AM (#40532826)
Passport offices care and may object.