I prefer case sensitivity, the filesystem shouldn’t do any magic like that. If someone types “file.txt”, opening “File.TXT” would be convenient, but also misleading. Ignoring case is what autocompletion/search is for imo.
The best things is when the OS enforces magic onto the filesystem. Ntfs is case sensitive but windoze is not. So expect some real fun times if you use ntfs on other systems.
Trying to rename a file to use the correct capitalization in a git repository on my Windows laptop for work was tricky. Or maybe it was subversion. Actually I think it was subversion. Either way it was a weird little puzzle for the day.
For real. It’s a ton of fun when you have a Linux server presenting a SMB share and you get a folder called MyFolder and one called MYFOLDER. Take a guess about what happens in that situation. I guarantee it’s different
I prefer case sensitivity, the filesystem shouldn’t do any magic like that. If someone types “file.txt”, opening “File.TXT” would be convenient, but also misleading. Ignoring case is what autocompletion/search is for imo.
The best things is when the OS enforces magic onto the filesystem. Ntfs is case sensitive but windoze is not. So expect some real fun times if you use ntfs on other systems.
Trying to rename a file to use the correct capitalization in a git repository on my Windows laptop for work was tricky. Or maybe it was subversion. Actually I think it was subversion. Either way it was a weird little puzzle for the day.
For real. It’s a ton of fun when you have a Linux server presenting a SMB share and you get a folder called MyFolder and one called MYFOLDER. Take a guess about what happens in that situation. I guarantee it’s different
I have a folder called backup and one called Backup shared over SMB… It is always Backup that gets opned.
Minor issue…NFS auto mount on most of my systems.