Post #2598119
2026-05-08 18:35 UTC
@pino@social.cologne if you prefer that behavior, then yes, that should be handled at a higher level than the filesystem. there is no reason to inject this ambiguity on a level where it can conflict with other systems.
my favorite problem case is this: you download a ZIP file or clone a git repository that has two files in it that only differ by letter case. good luck reading that on your case-insensitive system.
Replies (2)
-
@aesthr@wandering.shop 2026-05-08 18:38
@pino@social.cologne a case-insensitive system makes certain things impossible and causes incompatibilities. a case-sensitive one does not because it can still present to the user as mostly insensitive where possible.
-
@pino@social.cologne 2026-05-08 18:42
@aesthr@wandering.shop Sure it leads to problems when both worlds clash together. But isn't it a bit too simple to just blame the 'foreign' one? Also, higher levels could only apply workarounds. "paris" and "Paris" are two different file names here, and to me as an end user, that's typically not ideal, and no higher level can actually solve that in a clean way. But yeah, I'm fine with it since some decades, I'll be fine with it for the next some. :)