111–120 of 201 posts
Earlier quoted context omitted.
[flagged]
The fact is that there were so many character sets in use before Unicode because all these things were needed or at least wanted by a lot of people. Here's a great blog post by Nikita Prokopov about it: https://tonsky.me/blog/unicode/
Normalized code point sequences are another WTF feature.
Earlier quoted context omitted.
Regardless of the thorny question of whether it's Github's responsibility , it sure would be a good thing for them to do ASAP.
Here's the big reason GitHub should do it: It makes the product better I know people love to talk money and costs and "value", but HN is a space for developers, not the business people. Our primary concern, as developers, is to make the product better . The business people need us to make the product better, keep the company growing, and beat out the competition. We need them to keep us from fixating on things that a…
Making the product better generally stems from acting in their interest, honing the tool you offer to provide the best possible experience, and making business decisions that respect their dignity.
Your comment talks a lot about product and I agree with it, I just mentioned this so we don't lose sight of the fact this is ultimately about people.
Earlier quoted context omitted.
The fact is that there were so many character sets in use before Unicode because all these things were needed or at least wanted by a lot of people. Here's a great blog post by Nikita Prokopov about it: https://tonsky.me/blog/unicode/
Sometimes you gotta say no. Trying to please every hare brained idea leads to madness. Normalized code point sequences are another WTF feature.
I use non-Unicode mode in the terminal emulator (and text editors, etc), I use a non-Unicode locale, and will always use ASCII for most kind of source code files (mainly C) (in some cases, other character sets will be used such as PC character set, but usually it will be ASCII). Doing this will mitigate many of this when maintaining your own software. I am apparently not the only one; I have seen others suggest simil…
The biggest use of Unicode in source repos now might be LLM slop, so I certainly don't miss its absence at all.
Earlier quoted context omitted.
Unicode is about semantics not appearance. If you don't need semantics then use something different.
> Unicode is about semantics not appearance. And that's where it went off the rails into lala land. 'a' can have all kinds of distinct meanings. How are you going to make that work? It's hopeless.
Tell me what the problem is and what your proposed solution would be.
Earlier quoted context omitted.
What about numbers? Would they be assigned to arabic only? I guess someone will be offended by that. While at it we could also unify I, | and l. It's too confusing sometimes.
> While at it we could also unify I, | and l. It's too confusing sometimes. They render differently, so it's not a problem.