3 ms·

I mope at the lack of the latter, and it kept me off linux for twentysome years. Only now that I do most of my work in a GUI and I just click on filenames rathe

I mope at the lack of the latter, and it kept me off linux for twentysome years. Only now that I do most of my work in a GUI and I just click on filenames rather than typing them, does a case-sensitive filesystem not grind my gears. Every time I have to cd Downloads instead of cd downloads, I wonder who thought that was a good idea. Case-sensitivity is a classic case of users being forced to comply with the computer's needs, rather than the other way around. I contend that that is Wrong, period. To put it another way: Unicode is the opposite. It is computers adopting complexity to serve the needs of humans. If we can do unicode, we can do case-insensitive filename matching. If we're going to insist on case-sensitivity and ignore the needs of human language, we should just go back to plain old ASCII and force the humans to comply with that too.

mixmastamyk 6y ago
Try setting the insensitive option in your shell. With hidden filenames on mobile, desktop GUIs, terminal CLI completion, and shells with insensitive matching like fish (bash via option), the benefits of insensitive fs are not as high as they used to be. Meanwhile, the complexity of matching modern Unicode causes performance degradation and exposes many edge cases. In short, the window of time where insensitive made sense has largely closed.
- lmm 6y ago
  > With hidden filenames on mobile, desktop GUIs, terminal CLI completion, and shells with insensitive matching like fish (bash via option), the benefits of insensitive fs are not as high as they used to be. We've got better at working around case sensitivity, sure. I don't see that as a good reason not to fix the problem properly.
  - mixmastamyk 6y ago
    > Meanwhile, the complexity of matching modern Unicode causes performance degradation and exposes many edge cases. As mentioned, there is no way to "fix the problem properly" and a close-enough solution, rarely needed these days, slows performance.

mixmastamyk 6y ago

Try setting the insensitive option in your shell. With hidden filenames on mobile, desktop GUIs, terminal CLI completion, and shells with insensitive matching like fish (bash via option), the benefits of insensitive fs are not as high as they used to be. Meanwhile, the complexity of matching modern Unicode causes performance degradation and exposes many edge cases. In short, the window of time where insensitive made sense has largely closed.

lmm 6y ago
> With hidden filenames on mobile, desktop GUIs, terminal CLI completion, and shells with insensitive matching like fish (bash via option), the benefits of insensitive fs are not as high as they used to be. We've got better at working around case sensitivity, sure. I don't see that as a good reason not to fix the problem properly.
- mixmastamyk 6y ago
  > Meanwhile, the complexity of matching modern Unicode causes performance degradation and exposes many edge cases. As mentioned, there is no way to "fix the problem properly" and a close-enough solution, rarely needed these days, slows performance.