Although you can now run a number of Linux distros natively on Windows 10, this integration has been a little tricky when it comes to handling filename case, as Linux is case sensitive and Windows is not.
In order to overcome this limitation, starting with the Windows 10 April 2018 Update (version 1803), NTFS includes a new flag that you can enable on a per-folder basis allowing the file system to treat files and folders as case sensitive.
I’m sure there are countless technical reasons as to why case sensitive is the preferred route to go, but is there a case to be made for case insensitivity being simpler and less confusing to use?
If all you have are Western languages maybe, but “case” is not a universal language construct. It’s meaningless to do a case-insensitive compare of Arabic, for example.
Magical “do what I want, not what I say” behavior in a filesystem is already dangerous enough, having that behavior hinge on the character set is even worse.
Edit: I read too fast. You’re asking for good reasons for genuine case-insensitivity in file system operations. I can’t think of any.
Edited 2018-05-29 23:59 UTC