3 ms·
As a developer I could see case-sensitive file systems as more "proper" and predictable. But as an everyday Mac user, I'd be annoyed if I accidentally selected
by babl-yc 12y ago
As a developer I could see case-sensitive file systems as more "proper" and predictable. But as an everyday Mac user, I'd be annoyed if I accidentally selected "upload.png" instead of "Upload.png" and sent the wrong file.
- Shivetya 12y agojust as with programming languages, case sensitivity seems to me to purposefully introducing the possibility of errors.
- userbinator 12y agoBut as an everyday Mac user, I'd be annoyed if I accidentally selected "upload.png" instead of "Upload.png" and sent the wrong file. That assumes you somehow created two files with names differing only in case, which I'd argue would happen only if you were naming your files with such generic names. Also, I don't think the fact that two files' names look similar should be any reason to treat them as the same - otherwise, would you suggest that the letter O and the number 0 (along with the letter o) should be considered identical for filenames?
- FreezerburnV 12y agoYou obviously don't understand how a lot of people actually use their computer: http://xkcd.com/1459/ http://xkcd.com/1459/ (please note the tongue firmly planted in cheek, even if a lot of people actually DO work like this. which is terrifying)