Comment by thrwyoilarticle
4 years ago
There's a tendency away from snake_case and towards kebab-case in things you interact with via CLI. Even moreso towards nocase.
Programs like Powershell eschew ease of use in CLI for readability in scripts.
4 years ago
There's a tendency away from snake_case and towards kebab-case in things you interact with via CLI. Even moreso towards nocase.
Programs like Powershell eschew ease of use in CLI for readability in scripts.
> Even moreso towards nocase.
Nocase (did I break a rule by writing it that way?) seems great when you're enmeshed in the domain and you can see the implicit separators, but then someone looks at your naming from the outside and you're guaranteed to have an 'expertsexchange' in there somewhere.
oh, fsck
Powershell is case-insensitive, so camelCase is only a writing preference
It's still verbose in places
Snake_case is problematic for including filenames in TeX also. This is a big no for me, even if I find it more readable than the other.