3 ms·
Don't underestimate the power of defaults. Also, this can trip up in several other contexts besides headers. For instance, someone renames a file in their repo
by outworlder 12y ago
Don't underestimate the power of defaults.
Also, this can trip up in several other contexts besides headers. For instance, someone renames a file in their repository, changing just a filename case. And then you'll have to scratch your head a bit to understand a git issue that will invariably arise when you pull in the changes. Unless you are fortunate enough not to have a deadline, you won't be so quick to reformat the machine.
This actually happened to me. In the end, it was quicker to spin up a linux vm than to reformat the machine.
EDIT: Also, you appear to have missed the part that says "There is a case sensitive option, but Apple actively hides it and doesn't support it." No support is really, really, really bad. Noone will deploy OSX machines formatted like that if it is unsupported.
- duaneb 12y agoI'm not saying reformat the machine, I'm saying don't depend on case sensitivity if you use a default configured mac. And if you do depend on it, don't use the default configuration of the mac. How hard is this to figure out? It's not like case sensitivity is inherently desirable or better, especially for source code, where I would argue it's actively confusing and a huge code smell.
- tambourine_man 12y agoOS X is primarily a consumer's OS. Every time a decision has to be made between making the life of the programer or the consumer easier, Apple will choose the latter.
- walterbell 12y agoOn iOS, Apple made a consumer-unfriendly change when they disabled virtual printing, e.g. local Print-to-PDF from any application to a virtual-printer app.