4 ms·
Check out GoboLinux's file system structure: http://www.gobolinux.org/index.php?page=at_a_glance http://www.gobolinux.org/index.php?page=at_a_glance
by fiatpandas 13y ago
Check out GoboLinux's file system structure:
http://www.gobolinux.org/index.php?page=at_a_glance http://www.gobolinux.org/index.php?page=at_a_glance
- bhauer 13y agoI 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.
- Pxtl 13y agoIck, 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.
- fiatpandas 13y agoIf 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
- bhauer 13y agoAgreed! 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.
- tekacs 13y agoBut 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. :/
- mistercow 13y agoThere's a difference between case sensitivity and case preservation. FAT32 and HFS+ are examples of case-insensitive, case-preserving file systems.
- tekacs 13y agoThat 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
- mistercow 13y agoIt 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?
- Pxtl 13y agoOther 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".
- function_seven 13y agoRetain 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.
- plorkyeran 13y agoCase 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.
- nobleach 13y agoIt'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.
- jorgem 13y agoEven that has some warts: For example, Why not "MountS", since other folders are plural: FileS, ProgramS, UserS
- fsckin 13y agoPerfect is the enemy of good enough.