7 ms·
Case insensitivity was a huge mistake in computing really. Most languages don't have cases and its very non trivial to convert between cases. Should have treate
by Gigachad 4y ago
Case insensitivity was a huge mistake in computing really. Most languages don't have cases and its very non trivial to convert between cases. Should have treated every char as completely unique.
Sure. At the user signup side, block emails that are too close in ways like case, but as a sender you should always treat them as unique emails.
- wereHamster 4y agotolower() works mostly well in ASCII and languages which don't have weird rules (=works mostly well in english).
- 3np 4y agoThe context is e-mail addresses, not English.
- stouset 4y agoI think that's GP's point: tolower() looks like it works well to English speakers but it's subtly wrong and will fail unexpectedly for people with other locales.
- gumby 4y agoThose rules are only weird to you, but perfectly reasonable to others, such as Turkish or German speakers…well, readers :-)
- msh 4y agoInternalization is hard. I think its too much to expect software written for a specific market to handle all languages in the world. Fx in danish we have 3 letters (æøå) that is not common in the latin alphabet. I cant go to germany or turkey and expect people to be able to write out those letters when doing input in a local system.
- MandieD 4y agoFun thing I've run into in a Germany-based but increasingly international company: German always spells out umlauts and eszetts when going to lower ASCII for email addresses ("Schäßler" -> "Schaessler"), but Hungarian does not. Not sure how Turkish ö and ü get fully lower-ASCII-ized there, but in Germany, they get spelled out "oe" and "ue" as if they were German ö and ü. This isn't as much of a corner case as one might think - there are a lot of people with Turkish names in Germany.
- gumby 4y agoI’m always amused by these kinds of nonsensical usage for Turkish in Germany (ü->ue) but the thing that really trips people up is that Turkish has two letters that look like i, one with the tittle and one without — in both cases. Germany relatively adopted an uppercase ß (and got it into Unicode) to try to help with case roundtripping but I’ve never seen it in the wild. And let’s not get into obsolete German Fraktur ligatures like tz or ch which also had no upper case equivalents.
- bmn__ 4y ago> Germany relatively adopted an uppercase ß (and got it into Unicode) The parenthetical part is true. It was an uphill battle, but not because of the consortium, but because of what the tropes wiki would describe as executive meddling. The adoption is not recent, but about 110 years old. You have the wrong idea because of sloppy journalism. > I’ve never seen it in the wild I see it all the time. Maybe you are undercounting. Pay attention to non-standard letterforms on hand-written signs, and you also have to include print media where someone substituted lower-case ß in absence of a glyph in a font. This is a typographic mistake, but the intent is clear.
- Dylan16807 4y ago> to try to help with case roundtripping I don't think that's right. It's used in certain contexts like all caps.
- School-Cotton 4y ago> as a sender you should always treat them as unique emails This is already how it works. Senders are not supposed to assume that local-parts are case-insensitive. (Some buggy implementations ignore this requirement and upper-case everything, but the serious implementations don’t).
- OccamsMirror 4y agoThat's a surefire way to increase customer support load, as users have mix case for their emails all the time. They might sign up on a phone, or login on a phone. They might just be hamfisted. Sure, it might be their problem, but they'll make it yours.
- kalleboo 4y agoAnd people forgetting caps lock down for their passwords is so common that many UIs actually show a little caps lock icon in there to warn you
- Beltalowda 4y agoSo if my email is HeLLo@example.com because I want to be cute people will have to try 6 times before they finally get the right email address? Imagine telling that to someone in person. This kind "weird" casing isn't that rare and doesn't require cute usernames: "DonaldDuck@example.com", "FreeBSD@example.com", "DrMcCoy@example.com", etc. Languages that don't have case is not an issue; the situations where a lowercase <-> uppercase mapping is not simple are actually not that many. It's not trivial, but not all that complex either. The most annoying part is Turkish, Azeri, and Lithuanian where the rules differ a bit but the used language is often unknown. For the purpose of matching things ("is this email address known in our system?") it's actually not that hard, since you can just treat several characters as identical (displaying text correctly to users is harder, but that's not important here). I see this attitude in various situations, often under "falsehoods programmers believe" articles, which goes something like "it's hard in a few rare cases, therefore we should not do it at all for the >99% cases where it's simple and unproblematic".
- jstanley 4y ago> So if my email is HeLLo@example.com because I want to be cute people will have to try 6 times before they finally get the right email address? Imagine telling that to someone in person. Yeah. That's fine. If my email is LLLLLLLLLLLL@example.com because I want to be cute I have to tell people to type exactly the right number of L's. Do you think they should just be able to type a lot of L's and as long as it's somewhere near it counts as the same email address? In a world where email addresses are always case sensitive, everyone will use lowercase (like they pretty much always already do anyway), and it'll be fine.
- Beltalowda 4y ago"LLL@" doesn't map to "LLLLLLLL@" in any logical way. "lll@" does; that's just a silly argument.
- TylerE 4y agoIt also maps to 111@ and III@, depending in font
- fsckboy 4y ago> Case insensitivity was a huge mistake in computing really original ASCII only had uppercase. When lowercase got added, gradually with newer systems and software, without case insensitivity you would have had massive incompatibilities which probably would have hampered or even arrested the introduction of lowercase in new systems and all over again, when microcomputers first came out, they came out with uppercase only to cut complexity and cost on simple systems.
- spullara 4y agoThis was the original mistake. Encoding the font into the letter representation.
- pjc50 4y agoPossibly, but this dates back to .. maybe the 7th century and Carolingian Minuscule?
- samatman 4y agoCapital letters aren't a matter of font. There's a difference between the river phoenix, a magical bird which lives by the river River, and River Phoenix, the actor. It isn't a presentation-layer difference, it's an encoding-layer difference.
- jeffbee 4y agoI don’t see how adding lowercase to ASCII could have resulted in massive backwards compatibility issues considering that uppercase-only ASCII existed for only a few weeks in 1963. Surely there was not widespread adoption of ASCII in the spring of 1963.
- msh 4y agoDo you have any data to back that most languages dont have cases?
- umeshunni 4y agoOnly latin and Cyrillic scripts (or more broadly, alphabetic systems) have cases. Abjads, abugidas and logo/syllabic systems don't have cases.
- gumby 4y agoMost alphabets don’t have case (Devanagari, Arabic, etc) and many don’t have letters at all (Chinese, Japanese, et al). Case is only used in a few alphabets, mainly Latin-, Cyrillic-, and Greek-derived ones.
- msh 4y agoAre they a majority of languages if counted? I guess it also matters if you count the number of languages or if you count the number of people writing them.
- gumby 4y agoLet’s just use Greek and its descendants (Latin, Greek and cyrillic alphabets) and Brahmic-derived writing (we said “alphabet” when I was a kid but now ppl say “ Abugida“. There are about 200 languages spoken in Europe, all of which use these alphabets. India has over a hundred “major” languages and about 1600 others, most of which use Bramic writing alphabets (the major exception, Urdu, uses a form of Arabic writing). So a big imbalance! Oh, you want speakers? merely counting people who read Hanzi + Arabic-Alphabet readers + the Indian subcontinent gets you more half the world‘s population. And there are hundreds, maybe over a thousand writing systems.
- bmn__ 4y ago> in Europe, all of which use these alphabets Latin is much more wide-spread than that! You neglect whole of America and Australasia and half of Africa. https://upload.wikimedia.org/wikipedia/commons/9/9d/Writing_systems_worldwide.png https://upload.wikimedia.org/wikipedia/commons/9/9d/Writing_... > So a big imbalance! When we sum up realistically, then world-wide the amount of users of writing systems with case/"cameral" are about equally balanced with those without.
- gumby 4y ago> Case insensitivity was a huge mistake in computing really Ah, youth. There was little choice! Sometimes you had only six bits for a character; sometimes your bytes could be from 1-36 bits wide, depending on what you wanted for your program, so you might have systems that mixed six-bit (only upper case) and early ascii (two cases) and so for matching you had to be case insensitive. It’s easy to look back and say “those people were so stupid” but they weren’t.
- croes 4y agoComputer have to adapt to people and not the other way around. E-Mail wouldn't have been widely accepted with case sensitive addresses. People expect that MyName@mail.com reaches the same person like myname@mail.com or Myname@Mail.COM just like letters reach their recipient irrespective of the upper and lower case of the recipient's name. Computers are there to make the lives of the users easier, not the programmers.
- Aethylia 4y agoI'm not sure this is true. In my experience a lot of people actually do think that it's case sensitive. Many times I've heard someone describe the capitals while verbally telling someone their addresss. However it being insensitive has probably helped a lot of times where people make mistakes in explaining or copying those capitals.
- croes 4y agoRegarding email it doesn't hurt to think they are case sensitive but opposite would be a massive problem
- Gigachad 4y agoAs a sender, you should always treat email as case sensitive. As an email host/receiver, you can and probably should chose to be insensitive. But never assume any other host works like that. Similar to how gmail ignores . in emails but other hosts do not.
- tsimionescu 4y ago> In my experience a lot of people actually do think that it's case sensitive. I don't think they really do. They may think case matters somehow, and so may be careful to reproduce the exact case that they used before, but I don't think many people would expect JohnDoe@gmail.com and johnDoe@gmail.com to be too different email accounts.
- ghaff 4y ago
- cm2187 4y agoI think anyone who deals with end users would disagree. It seems impossible to get users to abide to a specific casing. Things would break all the time.
- koheripbal 4y agoThen again, if we could start from scratch we'd probably just have a single global phonetic language without case and with a limited number of total chars.
- saalweachter 4y agoHonestly non-phonetic glyphs are probably an easier lift. Fun fact: the reason we pronounce "ph" like "f" is because the Greek letter was originally pronounced like p-h, at the time Romans began stealing words, but then the Greeks started pronouncing it like "f" and the Romans followed suit, but kept the old Latinization of "ph", because they'd already carved it into stone. English spelling is largely phonetic... but it captures the phonetic spelling across dozens or hundreds of shifts in the spoken language. Unless you can stop people from changing how they speak, any phonetic spelling reboot is either going to suffer from the same problem, or words will constantly change how they are spelled to keep up with the spoken word.
- BeFlatXIII 4y agoChina has the proper idea for a writing system this entire time.
- paulmd 4y agoif you view meme culture as a trend towards increased symbol density in linguistic communication due to their ability to convey emotions, overtones, implications, and other nuance ("shaka, when the walls fell") then the increased symbol space of chinese/japanese/korean characters looks interesting. conversely it's certainly been an obvious disadvantage (posed a lot of problems and imposed a lot of awkward workarounds) for mechanical/electronic communication - now you have to enter the characters too, and you have to express that larger number of characters efficiently. In practice, a lot of electronic communication is just simplified to ASCII because that's the set that works universally. Someone used the example of ess-tset being transliterated as "ss" in german, dunno if chinese uses anything similar, but it wouldn't surprise me, obviously Japanese has romaji too. but at a human-interface level, fundamentally there is a limit to how many symbols people can absorb. Even with latin characters, people at best will sight-read whole words to increase symbol rate, but, the natural evolution is to use 1 character to represent 1 symbol/word, that's the highest possible rate at which humans can absorb symbols for a written system. And in turn you could in principle absorb a "word of symbols", which is a sentence, similar to how western readers can sight-read a word of our 1-character glyphs. by "increasing the dimensionality" of the symbol, you increase the effective symbol rate, similar to how memes use subtext/etc to convey more nuance than a pure text can by itself.