3 ms·
If you want case insensitivity at all, the filesystem is the wrong layer at which to implement it. If instead you implemented it at much higher level in userspa
by lemoncucumber 8y ago
If you want case insensitivity at all, the filesystem is the wrong layer at which to implement it. If instead you implemented it at much higher level in userspace then it would avoid a lot of complexity in the kernel and also result in a more useful feature for users.
I primarily use a Mac, and I don't think I've ever taken advantage of the case insensitivity. The only time I open files is by choosing them graphically or by tab-completing their names in my terminal or my editor.
The fact that case insensitivity is implemented at the filesystem layer rather than higher up means that my shell is still case sensitive, so I can't type "m<tab>" to autocomplete "Makefile" -- I have to type "M<tab>" instead.
Things like Spotlight or my IDE, on the other hand, implement their own case-insensitive filename search that works fine regardless of whether the underlying filesystem is case-insensitive or not.
- Someone 8y ago”so I can't type "m<tab>" to autocomplete "Makefile" -- I have to type "M<tab>" instead.” Many shells can do case-insensitive autocomplete. For example, in bash (https://askubuntu.com/a/87066 https://askubuntu.com/a/87066): set completion-ignore-case On in csh (https://stackoverflow.com/a/3306469 https://stackoverflow.com/a/3306469): set autolist = ambiguous set complete = enhance
- lemoncucumber 8y agoRight, but that's exactly my point: having it in the filesystem doesn't help with actual day-to-day use cases, since you still have to reimplement it in the shell if you want it there.