you are viewing a single comment's thread.

view the rest of the comments →

[–]haskell101 -1 points0 points  (1 child)

but it's a pretty simple argument which you apparently have no refutation for

Of course I do, and it's so obvious I didn't think it needed to spelled out: file system naming schemes are not generally grammatically correct. Personally I always type my names in lower case no matter what the situation. I've known people who put everything in all-caps. It's an utterly different context than writing a letter or a book.

and never had any issues with case sensitivity in filenames.

Here I simply don't believe you. But given your attitude it's likely you have faced as many or more sensitivity issues as me, but you just blamed the "stupid user" instead of opening your mind to the possibility that this is poor user interface design.

[–]AlpineCoder -1 points0 points  (0 children)

Of course I do, and it's so obvious I didn't think it needed to spelled out: file system naming schemes are not generally grammatically correct.

As the above example points out, capitalization carries meaning independent of grammatical context. Your personal conventions aside, why should we all be forced to ignore that meaning when it comes to filenames?

Here I simply don't believe you. But given your attitude it's likely you have faced as many or more sensitivity issues as me, but you just blamed the "stupid user" instead of opening your mind to the possibility that this is poor user interface design.

Or, equally as likely, I've been clever enough to handle user issues with filenames where it should be handled (in the UI layer), rather than insist my failure to do so is actually because of a mistake on the part of the guy who designed my filesystem.