4 ms·
Aside from having to import data from case-sensitive environments, could you give an example of a case where you would actually /want/ you filesystem to be case
by mortil 15y ago
Aside from having to import data from case-sensitive environments, could you give an example of a case where you would actually /want/ you filesystem to be case-sensitive? When would it ever, be a good idea to have two distinct files called readme.txt and README.txt?
- silentbicycle 15y agoI really wish I could remember the specific example. We used camelCase for filenames on that project, and there were two distinct names (like "bookcase" and "bookCase") that did not sound alike, yet were the same letters. The sort of thing that meant something very different if you moved the space. I prefer case-sensitive filesystems because the separation between works is semantically meaningful in English.
- masak 15y agoExample: checking out a repository where someone named (say) a file 'foo' and a directory 'Foo'. It happens. Most of the time that checkout will simply fail. Having this not work is less than enjoyable.