I always bring this up when people talk about case sensitive/insensitive. Traditionally, a machine only sees the difference in glyphs, not in letters. 'a' is a

I always bring this up when people talk about case sensitive/insensitive. Traditionally, a machine only sees the difference in glyphs, not in letters. 'a' is a different glyph to 'A'. We are used to dealing with case sensitivity because that's the most common instance in the English language where we have collision in meaning but not in glyphs. Let's take other non-latin characters, like accented letters or cyrillic. Some of these alphabets have letters that act as 'a' but are not 'a'. Some of these alphabets have glyphs that look like 'a' but are not 'a'. All of these glyphs are encoded using different codes as seen by a machine. If you want to support 'a' == 'A', then I could argue that I would want you to support 'a' == 'A' == <letter in cyrillic that means 'a'>. It is a very slippery slope, in my opinion. Logically, I would rather have 'a' and 'A' separated to avoid ambiguity, but feel free to disagree.