this post was submitted on 25 Apr 2025
3 points (100.0% liked)
Linux
14021 readers
568 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Good for him. I hate case-sensitivity, and it's what keeps me going back to DOS & Windows. FILE, File, file, and FilE should all be the same thing at all times.
"FILE, File, file, and FilE should all be the same thing at all times." - Sentences from the utterly deranged.
If these were truly the same thing, you should have not written them differently.
But you did.
Remember that 99% of the time that's gonna be because of a typo for 99% users. They won't have
File.txt,FILE.TXTandFiLe.tXt, they'll haveReportMay.docxandREportMay.docxor whatever.And yeah, that includes me. I don't want case-sensitivity for that reason alone. Thanks, but no thanks.
I prefer computers do what I tell them to rather than what it thinks I meant to tell it to. If I screw up, why isn't it on me to fix it? And why aren't you proofing data entry before accepting it?
Was this really supposed to be a clever point?
it's not "supposed". It just is.
Why shouldn't I be able to have the files mare.png (a photo of a horse) and MarE.png (a photo taken on a vacation in March, fifth in the series after MarA, MarB, MarC, and MarD)?
Or rainsley (a text file, no extension, with notes about a story I'm writing) and Rainsley (a directory with art of the same character the file is named after)?
Do I strictly need to be able to do these things? No, of course not. But the file system is more flexible and functional if I am able to.