I agree! There really should be no excuses at this point... you'd think. Even in 2008 I already felt we were behind the loop, but apparently I was vastly underestimating how bigger companies just dgaf.
And here I was typing out iso-8859-1
like a scrub to make sure I wasn't misremembering the encoding when doing the analogous thing in python...
Wait Beyonce is a blonde white woman now? Is this what they mean when they say “it’s a different kind of white?”
It's just skin tone, with the right lighting and color grading we all just look like people
i thought the top bit was originally 0 or 1 depending on the evilness/odiousness of the rest of the number, as a parity check.
The standard itself is 7-bit, since wires were deemed more valuable than endpoint logic for the teletype machines way back then. If you're running it on an 8-bit byte machine you could do it either way, although I'm not sure what the point in parity checking individual characters is. Modern software uses 0.
You've been able to do diacritical marks with ASCII for over thirty years. It's already standard. alt+0233
dunno if it's the same character but alt+130 has been firmly drilled into my brain from my entire Pokémon childhood.
Yeah let's drop wide characters, it was a bad idea. Let's simplify.. also let's convert all porn back to ASCII art.
Not true.
the Prince symbol is not eligible for inclusion in Unicode, which “does not encode personal characters, nor does it encode logos.”
Source: https://parkerhiggins.net/2013/01/writing-the-prince-symbol-in-unicode/