I don't think it's intended as a "solution", it just lets the clobbering that is caused by the case insensitiveness happen.
So git just goes:
If you add a third or fourth file ... it would just continue, and file gets checked out first gets the filename and whichever file gets checked out last, gets the content.
Depending upon their genre and your city’s size, they may never come nearby you
The joy of living in a central, densely populated area of Europe ... I've been able to see almost all niche bands that I'm into live.
The problem with that is that they are usually in tiny venues, often with no seating (some of us have issues with standing for a few hours straight), and absolutely terrible acoustics.
Not true at all where I live, except for the seating part sometimes. There are many small to midsized venues with ticket prices well below €50, and they all have way better accoustics than the large concert halls, and it's a much more personal experience than in a >10,000 people venue because you can be way up close with the artists.
For example, these are all venues I've visited in recent years, I rarely paid more than €30 for a ticket:
It tells you there's a name clash, and then it clones it anyway and you end up with the contents of README.MD in README.md as an unstaged change.
That’s some suckless level cope
Thanks, really constructive way of arguing your point...
Who really cares about some programming purity aspect?
People who create operating systems and file systems, or programs that interface with those should, because behind every computing aspect is still a physical reality of how that data is structured and stored.
What’s correct is the way that creates the least friction for the end users
Treating different characters as different characters is objectively the most correct and predictable way. Case has meaning, both in natural language as well as in almost anything computer related, so users should be allowed to express case canonically in filenames as well. If you were never exposed to a case insensitive filesystem first, you would find case sensitive the most natural way. Give end users some credit, it's really not rocket science to understand that f and F are not the same, most people handle this "mindblowing" concept just fine.
Also the reason Microsoft made NTFS case insensitive by default was not because of "user friction" but because of backwards compatibility with MSDOS FAT16 all upper case 8.3 file names. However, when they created a new file system for the cloud, Azure Blob Storage, guess what: they made it case sensitive.
Unix was designed for mainframes
Unix was never for mainframes. It was for 16-bit minicomputers that sat below mainframes, but yes they were more advanced than the first personal computers.
It’s actually impressive how much modern/business functionality they were able to cram into that.
Absolutely, but you have to admit that it's a less solid foundation to build a modern operating system on.
In the 80s, there were several Unices for PC too btw: AT&T, SCO, even Microsoft's own Xenix. Most of them were prohibitively expensive though.
Platforms like reddit and Tumblr benefit from a friction-free sign up system.
Even on Reddit new accounts are often barred from participating in discussion, or even shadowbanned in some subs, until they've grinded enough karma elsewhere (and consequently, that's why you have karmafarming bots).
Is this a problem here?
Not yet, but it most certainly will be once Lemmy grows big enough.
You're probably joking, but in case you don't know: LPT stands for Line Printer Terminal, and LPT1, LPT2, LPT3... referred to parallel ports which were typically (though not exclusively) used to connect a printer.
The thing is, a lot of the legacy backwards compatible stuff that's in Linux is because a lot of things in Unix were actually pretty well thought out from the get go, unlike many of the ugly hacks that went into MSDOS and later Windows and overstayed their welcome.
Things like: long case sensitive file names from the beginning instead of forced uppercase 8.3 , a hierarchical filesystem instead of drive letters, "everything is a file" concept, a notion of multiple users and permissions, pre-emptive multitasking, proper virtual memory management instead of a "640k is enough" + XMS + EMS, and so on.
Or just name the file con. Windows 95 even used to bluescreen if you tried to refer to con\con.
To screw with Windows users, you should sometimes put a README.md as well as a README.MD in your git repos. It leads to interesting results.