Wait wait wait wait Am I the only one who didn't know this?? #rstats
6
4
1
20
Sorry to possibly bursting your bubble but what you observe is a side-effect of being on an operating system that threats filenames as case-insensitive. Hello macOS. "Real" operating systems do not do that. What your tweet celebrates as is more of a bug than a feature. #rstats
1
1
24
Quick demo on non-macOS below.
2
1
2
While one _can_ it is not the default, and that is the bug. No excuses, macOS is wrong here and should have known better. Just how Windows should not have trampled on POSIX behaviour in its core library. Too late now, but we (in aggregate) wasted millions of developer hours.

Jan 9, 2023 · 5:18 AM UTC

1
1
Agree. If they had a sensible default, it would avoid a lot of headaches.
1
1
I cannot tell how often I got code or patches with, say `#include "Abc.h"` failing to compile because the file, at my end, would be `abc.h`. It is beyond stoopid, and all Cupertino's fault.