4 ms·
It's PascalCase, rather than camelCase, but I still agree with your point - capitalisation in a Linux file system just feels... weird!
by GordonS 5y ago
It's PascalCase, rather than camelCase, but I still agree with your point - capitalisation in a Linux file system just feels... weird!
- pxc 5y agoI like initial caps for directory names and lowercase for filenames, which Linux desktop users are already accustomed to in their home folders. Caps leading command names is not great with case-sensitive filenames imo.
- petre 5y agoI always change my home folders to a lowercase shorthened version and modify ~/.config/user-dirs.dirs. Of course, when you do an accidental rm -rf you're at disk to erase ~/work, but that's what regular backups are for. Expanding capitalisation to the whole filesystem hierarchy is a no go for me, it would only waste my time and further degrade my productivity. I also never liked Pascal, Java and C# specifically because of the weird capitalisation conventions which in my view makes the code look messy. PowerShell? Just call the exorcist.
- nmz 5y agoFWIW I tend to put directories first character as Uppercase and files as lowercase. this is useful when sorting and also identifying what type of file something is (so long as its a file I created).
- galaxyLogic 5y agoA file or folder can have a name with mixed uppercase and lowercase characters. That name would show in the directory listing. But it should be addressable case-insensitively. And it shouldn't be possible to create two or more separate files in the same directory which differ only by case.
- nmz 5y agoAlas, in unix, there's {mkdir A a;touch A a} Which is sometimes useful, but I see what you're saying.