3 ms·
I very strongly advise to NOT ever use a case-sensitive file system. While in this case we have an example of software the NEEDS case sensitivity, a lot of appl
by carterschonwald 14y ago
I very strongly advise to NOT ever use a case-sensitive file system. While in this case we have an example of software the NEEDS case sensitivity, a lot of applications folks use will BREAK (or would historically) when installed on a case sensitive file system.
Examples include: Dropbox, Steam, Photoshop.
I'm sure more recent versions of these software tools can handle case sensitive file systems (one hopes), but I can say with certainty that there is plenty of other software in the wild, especially if its origins date back using FAT or NTFS on WIN32.
In an ideal world, software would be written in a way that works fine on both Case and Case-Insensitive file systems, but we live in a world were software engineering is rarely so disciplined.
point being: if you want to use any interesting desktop software that at some point may have been targeted in part at WIN32 systems in some past era, please make sure you stay with a case INsensitive file system
that was my PSA for the day/week/month
- hollerith 14y agoHope everyone realizes that by default, os x's file system is not case sensitive. (Case preserving, yes.)
- mitchty 14y agoYep, its no different than NTFS really. I just wish developers would test their apps out on case sensitive filesystems so we could use them.
- richardwhiuk 14y agoWhy? Case Sensitive file systems are a truly ridiculous idea. I can't imagine anything more annoying than having README and Readme being two different, independent files...
- mitchty 14y agoI guess I find it more annoying that they're preserved but sensitive. Typing LS and having it work is... odd.
- clhodapp 14y agoYou are correct. In practice, case-sensitive filesystems on OS X are impractical, but boy does this destroy my faith in developers... how hard is it make sure that you use the same cases in your paths throughout your program?