3 ms·
> What troubles do they cause? Once, a colleague working on Linux created two files with same name but different case, and committed them to the Git repo, and
by skissane 7y ago
> What troubles do they cause?
Once, a colleague working on Linux created two files with same name but different case, and committed them to the Git repo, and then I tried pulling it on my Mac. I don't remember exactly what happened next, but I wasted a lot of time trying to sort that mess out.
(There was no real reason for them doing this, it was just a mistake on their part, and they didn't notice they'd done it before committing the files.)
- bendiksolheim 7y agoYou could argue that this is a problem with case sensitive file systems, not insensitive ones. In fact, this could never happen on a case insensitive file system, as you could never create a file named the same but with a different case. It seems to me that most problems with case insensitive file systems are rather problems because there are different file systems out there. Just as there always is with "competing" standards.
- angry_octet 7y agoThe whole idea is hopelessly tied to ascii notions of alphabet, where two functions (storage a retrieval with keys, and searching for matching keys with the UI) have been conflated. What is 'case insensitive, case preserving' in Unicode for Korean or Chinese or Arabic? It doesn't remotely make sense to make some keys illegal in the file system layer for reasons of disambiguation.