Nothing to do with Linux, and everything to do with case sensite filesystems common on UNIX.
macOS uses case insensitive filesystem by default for backwards compatibility with HFS+.
You can turn case sensitive on HFS+ and APFS if so desired for the "Linux" experience, via Disk Utility or the equivalent CLI tool.
And if looking to have some fun on an ecosystem that doesn't expect it, you can equally turn it on on NTFS, via fsutil.
> > I'm painfully aware how much is developed by people with no access to or interest in MacOS. [...] Sometimes you can tell by the simple fact that the git repo contains files in one directory that conflict in naming. Linux has no issues with "Foo" and "foo" coexisting.
> Nothing to do with Linux, and everything to do with case sensite filesystems common on UNIX.
Of the three major desktop operating systems (Microsoft Windows, Apple macOS, and the Linux family), only Linux has case sensitive filesystems by default. Therefore, it's likely that someone who didn't care about filename case conflicts was running Linux.
Sometimes you can tell by the simple fact that the git repo contains files in one directory that conflict in naming. Linux has no issues with "Foo" and "foo" coexisting.