Remember that 99% of the time that’s gonna be because of a typo for 99% users. They won’t have File.txt, FILE.TXT and FiLe.tXt, they’ll have ReportMay.docx and REportMay.docx or 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?
Do you also turn off autocorrect? As for why I’m not proofreading my entries? I am. But typos happen. Try to put yourself into the shoes of the average office drone or consumer just using a PC as a tool. I’m pretty sure I’ve harped on this before, but most people aren’t experts or enthusiasts, they just want a working computer that’s as simple to use as possible. The benefits of a case sensitive-file system are far outweighed by how susceptible it is to user error.
Do you actually have a case sensitive filesystem? Because in reality I don’t even notice it when doing normal work. It seems like such a weird thing to be crying about.
I did, because they’re different ways of expressing the same meaning. They all mean (apologies for borrowing mathematical notation for linguistic applications) |file|. I don’t care what the expression of a thing is, I care about meaning. And as a result, when I save a file and then search to recall it, it should not matter what case it’s in - only for the meaning to match. The state of my shift or capslock should be totally immaterial.
Then why should it allow me to save different expressions of the same meaning ever? If it’s going to let me search for it case-insensitive, just head the matter off at the pass and save it that way. Either that, or automatically create link files for every case permutation to the same folder as soon as the file exists.
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?
Do you also turn off autocorrect? As for why I’m not proofreading my entries? I am. But typos happen. Try to put yourself into the shoes of the average office drone or consumer just using a PC as a tool. I’m pretty sure I’ve harped on this before, but most people aren’t experts or enthusiasts, they just want a working computer that’s as simple to use as possible. The benefits of a case sensitive-file system are far outweighed by how susceptible it is to user error.
Do you actually have a case sensitive filesystem? Because in reality I don’t even notice it when doing normal work. It seems like such a weird thing to be crying about.
I’ve used Linux, yes. And I’m not “crying” I just find it annoying. Good grief.
I did, because they’re different ways of expressing the same meaning. They all mean (apologies for borrowing mathematical notation for linguistic applications) |file|. I don’t care what the expression of a thing is, I care about meaning. And as a result, when I save a file and then search to recall it, it should not matter what case it’s in - only for the meaning to match. The state of my shift or capslock should be totally immaterial.
Whatever you use to search can just be case insensitive, which is how most file browsers work on Linux.
Then why should it allow me to save different expressions of the same meaning ever? If it’s going to let me search for it case-insensitive, just head the matter off at the pass and save it that way. Either that, or automatically create link files for every case permutation to the same folder as soon as the file exists.