Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What every software developer must know about Unicode in 2023

tonsky.me

Post reply on HN
Print view View original

101–110 of 572 posts

Re: What every software developer must know about Unicode in 2023

#101

Post by bigstrat2003 »

justrealist wrote: post #87

I don't want to be too full of myself here, but I'm a very skilled and highly paid backend software engineer who knows roughly nothing about unicode (I google what I need when a file seems f'd up), and it's never been a problem for me. I'm sure the article is good but the title is nonsense.

The title is definitely nonsense. The reality is that for most people, they will never need to know the gritty details of how to encode or decode UTF-8. The article is interesting, but I was pretty put off with how the author led with such a hyperbolic (and untrue) claim.

Re: What every software developer must know about Unicode in 2023

#102

Post by zbtaylor1 »

Luctct wrote: post #93
tr888 wrote: post #41

What on EARTH is that mouse cursor thing all about? Why would you even bother writing this, then making it impossible to read properly?

I don't know what you people are talking about. I'm just glad I always browse with Javascript turned off. If you didn't see the writing on the wall and permanently turn Javascript off around 2006, you have no right to complain about anything. Meanwhile, ironic irony is ironic: "Hey, idiots! Learn to use Unicode already! Usability and stuff! Oh, btw, here is some extremely annoying Javascript pollution on your screen…

Are you alright?

Re: What every software developer must know about Unicode in 2023

#103

Post by wyldfire »

> “I know, I’ll use a library to do strlen()!” — nobody, ever.

The standard library provided by languages like C, C++ is a library. Features like character strings are present and it's a totally reasonable expectation for the length to give you the cluster count.

Re: What every software developer must know about Unicode in 2023

#104

Post by bigstrat2003 »

badcppdev wrote: post #57
qwerty456127 wrote: post #16

> The rest, about 800,000 code points, are not allocated at the moment. They could become characters in the future. Why is Tengwar still not in Uniclde officially? What's the problem with it?

To save other people the google: Tengwar is probably not in unicode because it is a fictional script from a book.

Honestly, I wouldn't have thought that would be an issue to the Unicode folks. They have already allowed things (emoji) that have no place being in the standard, as they aren't even text.

Re: What every software developer must know about Unicode in 2023

#105

Post by DoughnutHole »

qwerty456127 wrote: post #23

> People are not limited to a single locale. For example, I can read and write English (USA), English (UK), German, and Russian. Which locale should I set my computer to? Ideally - the "English-World" locale is supposedly meant for us, cosmopolitans. It's included with Windows 10 and 11. Practically, as "English-World" was not available in the past (and still wasn't available on platforms other than Windows the last…

> I doubt many English speakers care to distinguish between English dialects

It's worthwhile purely for the sake of autocorrect/typo highlighting in text-editing software. I don't miss the days of spelling a word correctly in my version of English but still being stuck with the visual noise of red highlighting up and down the document because it doesn't conform to US English.

Re: What every software developer must know about Unicode in 2023

#106

Post by JohnFen »

dathinab wrote: post #66
oliwarner wrote: post #52

Earlier quoted context omitted.

It's tracking every visitors' cursor and sharing it with every other visitor. Why would a frontend developer demonstrate their ability to do frontend programming on their personal, not altogether super-serious blog? I meant that rhetorically but it's a flex. I agree, not the best design in the world if you're catering for particular needs, but simple and fun enough. You should check out dark mode. In that vein, I thi…

> Why would because it shows that they don't understand important design aspects while it doesn't really show off their technical skills because it could be some plugin or copy pasted code, only someone who looks at the code would know better. But if someone care enough about you to look at your code you don't need to show of that skill on you normal web-site and can have some separate tech demo. > okay if we let peo…

Not every website, even technical ones, need to have an eye towards professional advancement. Sometimes they're just for fun. I welcome it, as it's a thing that gets more rare on the web as time goes by.

Re: What every software developer must know about Unicode in 2023

#107

Post by JohnFen »

amelius wrote: post #94

Can we please get a standard that describes how emoji are supposed to look? Now they look different on every platform and many subtleties are lost in translation.

Yeah, this problem has led me to avoid using emojis. I can't be sure that the meaning I was intending is the one being depicted by the recipients machine.

It's probably a good thing, though.

Re: What every software developer must know about Unicode in 2023

#108

Post by JohnFen »

ilyt wrote: post #32

> Unicode is locale-dependent Well, there is a new fact that I learned and immediately hated. The fuck were authors thinking... I am now firmly convinced people developing unicode hate developers. I suspected it before just due to how messy it was (same character having different encodings ? Really ? Fuck you), but this cements it.

> people developing unicode hate developers

Or at least they have a vicious indifference to us. Unicode is a nightmare.

Re: What every software developer must know about Unicode in 2023

#110

Post by AnimalMuppet »

wyldfire wrote: post #103

> “I know, I’ll use a library to do strlen()!” — nobody, ever. The standard library provided by languages like C, C++ is a library. Features like character strings are present and it's a totally reasonable expectation for the length to give you the cluster count.

No, for C and C++, which are close to the hardware, it's totally reasonable to expect strlen() to give you the byte count. You don't allocate memory for buffers based on the cluster count.

If you want cluster count, call a different function.

Post reply on HN