Post #2598116
2026-05-08 18:10 UTC
@pino@social.cologne It's the fault of the OS vendor to allow (or even enforce) a case-insensitive filesystem in the first place. convenience features like insensitive search or autocomplete can and should work independently of the file system, but having ambiguity about file paths is a really bad problem at a very low level.
File paths are unique strings of characters, "a" and "A" are simply not the same character.
Replies (1)
-
@pino@social.cologne 2026-05-08 18:15
@aesthr@wandering.shop Unfortunately Linux doesn't even enforce that file names are valid UTF-8 or anything like that. So what *is* a character? I mean, yeah, sure, I know what you mean. I'm telling that since 20 years when people ask me. There were also times, though, when I had preferred case insensitivity a lot, from end user perspective. Sure, it's definitely a pitfall, because it can be surprising to novice devs.