I like it! I suppose I am a tad disappointed that it's a distribution in its own right. But they deserve credit for taking a decent first step.

Ick, capitalization in a case-sensititive file-system? Of course, as far as I'm concerned case-sensitivity is generally a misfeature in anything user-facing.

If I remember correctly, their scripts automatically convert lower case letters to uppercase when you are trying to autocomplete typing with TAB. It only does it for the gobolinux-specific uppercase directories

Agreed! I feel retaining case-sensitivity in file systems in 2013 is basically trolling users. I can think of no practical upside; only the opportunity for annoying jokes and tricks.

But what of users (as they often do) descriptively naming files?

I've seen plenty of "Accounts for Proctors' Attention.xlsx" style files. Case insensitivity would lose the case there. :/

There's a difference between case sensitivity and case preservation. FAT32 and HFS+ are examples of case-insensitive, case-preserving file systems.

That there is, but I'm inclined to suggest this behaviour to be more confusing than simply maintaining name identically to input. :/

Not least this can sometimes result in some odd corner cases.

shrug

It seems like the ideal case to me; generous on input, strict on output. In most cases, users won't even know that the insensitivity is there, in which case it will almost never affect them (since users very rarely want two files with the same name, differentiated by case). For users who do know about it, it's not confusing.

What corner cases does it lead to?

Other languages have capitalization rules that are far, far more complicated than English, involving additional characters that either denote capitalization or a semantically different word depending on context.

Personally, I'd aggressively pursue case-insensitivity and treat the problem of "oops the user can't create two files that have nearly the same name" as a much smaller bug than "oops the user can create two files have semantically the exact same name".

Retain the case, but don't use it when testing for uniqueness. That way, I can type "accounts for proctors' attention.xlsx" and the filesystem will know what I mean. But when I list the contents of a directory, it would show up with its original casing.

Case insensitivity is locale-dependent, so you have to either pick a single locale and confuse users with other locales, or deal with the possibility that you could have two files in your filesystem that have the same name in your locale.

It's not as big of a deal when you're using ZSH autocomplete... but I agree, I like my filesystem lowercase and devoid of spaces.

Even that has some warts: For example, Why not "MountS", since other folders are plural: FileS, ProgramS, UserS

Perfect is the enemy of good enough.