It would be awesome to redesign Unicode to not suck.
-
-
Replying to @cmuratori
What's wrong with it? I'm thinking it'd maybe be nice to not have multiple ways to represent the same accented character. Otherwise I'm struggling to see the problems, let alone outright suckage.
1 reply 0 retweets 1 like -
Replying to @XplodingCabbage
You can see the "suckage" just by looking at how infrequently applications actually handle Unicode correctly. There are vanishingly few. The specifics of why this is are many but not really a subject coverable in tweets.
1 reply 0 retweets 7 likes -
Replying to @cmuratori @XplodingCabbage
It is very difficult to find an ASCII-capable application that does not display all of ASCII's printable glyphs correctly. It is extremely easy to find a Unicode-capable application that does not display all of Unicode's printable glyphs correctly.
2 replies 2 retweets 8 likes -
Replying to @cmuratori @XplodingCabbage
The conventional wisdom here is that somehow it is the application developer's fault, but actually, it is just that Unicode is poorly designed and requires a tremendous investment in developer time to even attempt to get right.
1 reply 2 retweets 11 likes -
Replying to @cmuratori
Hmm. Speaking as a dumb application developer, my take is a mix of "application dev's fault", "bad &/or obsolete programming language design choices (e.g. strings as sequences of UTF-16 code units) lay traps for the naive", and "inherently complicated problem domain".
2 replies 0 retweets 3 likes -
Replying to @XplodingCabbage
Well, personally, I think it should go without saying that application developers should not be expected to comprehend a _one thousand page_ specification in order to display and edit text on the screen.
1 reply 0 retweets 15 likes
I think this is a simple case of overcomplicating something that should not have been complicated. You can see the design decision mistakes in Unicode - they mostly stem from them not realizing what should and shouldn't be explicitly encoded.
-
-
Replying to @cmuratori @XplodingCabbage
As a result, you take what should have been a relatively simple specification and you turn it into something that requires massive amounts of special-case "AI-like" coding to get right (tons of pattern matching, etc.)
0 replies 0 retweets 5 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.