4 ms·
>If you believe it should serve humans, then you understand why allowing a - prefix or case sensitivity causes unnecessary problems. Serving humans feels like
by fbdab103 3y ago
>If you believe it should serve humans, then you understand why allowing a - prefix or case sensitivity causes unnecessary problems.
Serving humans feels like it should take whatever garbage I shove down its throat and be happy to receive. Similarly, I think many humans would like to differentiate between, "resumefinal.docx" and "resumeFINAL.docx"
- lmm 3y ago> Similarly, I think many humans would like to differentiate between, "resumefinal.docx" and "resumeFINAL.docx" I strongly disagree. Those sound exactly the same. If you had a physical filing cabinet and asked someone to get a document from the final folder (which is supposed to be the human-friendly metaphor we're using here), they would happily open a folder labeled FINAL, and be quite confused if you had distinct final and FINAL folders.
- smackeyacky 3y agoIf they shout the name, you know to look for the upper case version :-)
- eviks 3y agoHumans don't speak binary garbage, so it's a disservice to them to happily swallow/spit it out Cap sensitivity is a much lesser mistake
- coldtea 3y ago>Similarly, I think many humans would like to differentiate between, "resumefinal.docx" and "resumeFINAL.docx" Would they? Both are the "final resume" Word document... Humans don't care about case in distinguishing names. Considering case differences as important distinctions between names (of files in this case) is something instilled from using computers, not a human trait. That's a concern for coders, proof-readers, and other OCD types. Not to mention that the most popular Desktop OSes (Windows, MacOS) don't care for file case either. They preserve it for visual display is you set it, but two filenames with differences in case only are the same file - and can't coexist.