Notices by divVerent (divverent@social.vivaldi.net)

@icedquinn @Suiseiseki @wolf480pl @a1ba TBH diacritics are less of an issue - most operations on strings can easily work on a per-codepoint basis, such as word wrapping - you just need to handle diacritics and other combining codepoints as if they're a word character.

And for stuff like line length computation, you need to take the different per-character width of your font into account anyway.

What's really annoying is string comparing, as you now have to apply a normalization first...

@Suiseiseki @wolf480pl @a1ba "It depends". UTF-16 is definitely faster to decode because you have fewer loop iterations for the same string (8bit and 16bit RAM reads are about the same speed on the CPU).

HOWEVER, especially when all codepoints are ASCII, UTF-16 uses twice the memory bandwidth. And that hurts too.

So, ultimately depends on the character set / language used.