Re:WorstFit: Unveiling Hidden Transformers in Windows ANSI
by cryptonector on Friday January 10, 2025 @11:53AM
(#42657363)
> IMO, case-insensitive filesystems are an abomination; the case-insensitivity should have been done in the user interface layer, not in the filesystem layer.
Implementing case-insensitivity in a file picker or something is OK, but doing that throughout your app's runtime is insane since you'd have to hook every file open and then list the directory, whereas in a file picker you're probably listing the directory anyways.
Re:WorstFit: Unveiling Hidden Transformers in Windows ANSI
by cesarb on Friday January 10, 2025 @01:32PM
(#42658479)
The file picker is precisely where case-insensitivity should be done; the rest of the application should already have the correct file name.
Re:WorstFit: Unveiling Hidden Transformers in Windows ANSI
by cryptonector on Friday January 10, 2025 @01:47PM
(#42658670)
Though you best not have a million files in that directory...
Re:WorstFit: Unveiling Hidden Transformers in Windows ANSI
by Dwedit on Friday January 10, 2025 @04:01PM
(#42660171)
Did not know about $UpCase, the only part I knew was that the FAT16/32 driver from Microsoft (Which has the source code officially released, it's used as an example for how to implement a filesystem on Windows NT) uses locale-specific case-sensitivity tests.
AFAIK, it's even worse: it uses the rules for the locale which was in use when the filesystem was created (it's stored in the $UpCase table in NTFS, or its equivalent in EXFAT). So you could have different case-insensitive rules in a single system, if it has more than one partition and they were formatted with different locales.
IMO, case-insensitive filesystems are an abomination; the case-insensitivity should have been done in the user interface layer, not in the filesystem layer.