2 ms·
some of the alternatives were simpler and deliberate attempts to reduce the scope of the migration problem. You can’t say “all approaches would have suffered t
by tonymet 6mo ago
some of the alternatives were simpler and deliberate attempts to reduce the scope of the migration problem. You can’t say “all approaches would have suffered the same migration effort” as if it’s a given. That’s like saying UTF8 and UTF16 had the same migration effort because they both tried to migrate from 1-byte code points. UTF8 was way easier.
- zadikian 6mo agoYeah and UTF-8 shouldn't be taken for granted. I always wondered why there's still UTF-16 in so many places, even Swift strings (apparently changed in v5)... It's cause that was the natural replacement for UCS-2, which for certain reasons was beating UTF-8 early-on.