Offtopic, but this kind of one-line conditions are typically best written as
test -d ~/dev/go && export GOPATH=~/dev/go
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.
Not all of them. You can choose to have a case-sensitive filesystem if you’d like.
Holy smacks, all these years and I never knew that! Too bad auto-complete doesn't pick up on it though.
It's like reading a book that uses three different fonts on each page. You just cannot take it seriously.
MacOS is one of the few registered UNIX systems out there (https://en.wikipedia.org/wiki/Single_UNIX_Specification#macO...).
I actually do not own a Mac, but it is a decent OS and performs well and tries to be windows friendly (hence camelcase and spaces) and tries to be stable and secure.
cool way to bloat your glyph set to double the size and introduce aesthetic and string matching problems.
In terms of your general point, upper and lower case letters were originally different stylistic type-faces rather than "modes" of a letter in the same type-face. It wasn't until relatively recently in our writing history that the rules of capital letters became defined rather than a style choice and I'm certain they weren't thinking much about the problems that might cause with string matching on digital systems invented several hundred years later.