[sneak]

File systems on macOS are case insensitive. The system-provided directories are capitalized by convention, but you may also refer to them in lowercase if you like. It’s no more a “red flag” than `c:\WINDOWS` being capitalized.

I opt for the if-brackets rather than the one line syntax because it is clearer to read. “if this, then that” is less mental effort than remembering just how boolean operators short circuit, for me at least. It's a few extra lines but I prefer the layout, indent, and ease of scanning.

[flukus]

Windows now has optional case sensitivity on a per directory level. Drove me crazy trying to work out errors in an old c# codebase after a git checkout in wsl, multiple rounds of screaming THE FILES RIGHT THERE!

[saagarjha]

> File systems on macOS are case insensitive.

Not all of them. You can choose to have a case-sensitive filesystem if you’d like.

[sneak]

As of about five years ago, enabling that feature at mkfs time broke tons of apps that assume case insensitivity. Not sure if the situation has improved.

[yesenadam]

Speaking of filename weirdness.. I changed my Mac's language to Spanish a few years ago, as I was learning the language, which has many bizarre effects, online and off. One is that the Library folder in my home folder appears in Finder as Librería, yet if I try to cd to Librería or Libreria in bash it doesn't work, as it's actually Library. Same for Documentos, Imágenes, Aplicaciones, Escritorio (Desktop), Usuarios, Sistema etc. I haven't looked into how that actually works. But there seems something very wrong about files appearing as not what they're called, which I assume the whole non-English-speaking world puts up with.

[ImprovedSilence]

> File systems on macOS are case insensitive.

Holy smacks, all these years and I never knew that! Too bad auto-complete doesn't pick up on it though.

[xyzzy99]

It can. Try: set completion-ignore-case on (for bash).