I reject the idea that MySQL's shitty unicode behavior is because it predates UTF8. Postgres is only one year younger.
-
-
Replying to @sgrif
>Reading UTF-8 white paper "Hmm. It calls for up to 4 bytes. But 3 bytes should be good enough for anyone" >Later, emoji "Well shit"
2 replies 0 retweets 0 likes -
Replying to @FakeUnicode
Not that indexing by codepoint is a useful operation for 99% of applications.
1 reply 0 retweets 0 likes -
Replying to @sgrif
Their "utf8" (without _mb4) being a broken subset of UTF-8 seems a bigger deal than "Z" coming first alphabetically before "a". >_<
2 replies 0 retweets 0 likes
Replying to @FakeUnicode
(Code example in question: http://docs.diesel.rs/diesel/expression/expression_methods/escape_expression_methods/trait.EscapeExpressionMethods.html#example …)
2:32 PM - 6 Feb 2017
0 replies
0 retweets
0 likes
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.