4 msΒ·
I'm actually more annoyed that they are there in the first place. Unicode can't seem to decide whether it's about just encoding text or also doing presentation
by clarry 6y ago
I'm actually more annoyed that they are there in the first place. Unicode can't seem to decide whether it's about just encoding text or also doing presentation/formatting (and now piles of poo and colorful emoji, what next, animations?), so now it's a bit of both, what a mess. It's making life hard and breaking things for applications that assume text is just text, and the presentational features are not enough to avoid having to implement your own presentational features in a program that needs to do presentation..
now you have applications where you can't find a string because it was written in Unicode bold letters instead of the letters' normal ASCII counterparts. And then you have applications that are confused about those bold letters because they are not actually surrounded by bold markup.
The worst part is that you can't criticize unicode without attracting a crowd of bullies who handwave about human languages being complicated (no, that does not justify poor design) or say it has to be this way because ugh shift-jis (or whatever nasty old encoding you can come up with) is not nice.
Well designed technology makes complex things simple. People defending poorly designed technology blame the problem for being complex.
π½π¦ππ π¦ππππ ππ!
(Why don't you try search for "fuck" in Firefox?)
- GekkePrutser 6y agoYou're so right... Unicode is making things too complex, and intruding on various formatting issues. Case in point: The skin tone modifiers. Or this stuff: https://en.wikipedia.org/wiki/Zero-width_joiner https://en.wikipedia.org/wiki/Zero-width_joiner There doesn't exist any parser that does it 100% correct. And parsing it is becoming so complex that it's causing bugs and vulnerabilities (it's not a coincidence that so many remote exploits use some kind of unicode to trigger it).