This is really a problem of human vs computer thinking.

F and f are two different characters, encoded differently. Ergo, File and file are different by raw bytes.

Some developers wish to make the interactions for the user more consistent and thus a case-insensitive filesystem is born. The problem is that this is such a low level place to make this decision.

A filesystem, as in the kernel level interactions for files, should be case-sensitive in that every character is a unique series of bits. But there’s nothing stopping a higher level api from helping users out. It would be sensible to have a case-insensitive desktop environment.

The low level functionality should remain intentional though.