The reason I'm complaining:
- Software uses an emoji picker which hasn't been updated in a while.
- I forked it and switched to Noto emojis which are up-to-date.
- Noto emojis use a different naming scheme from Twemojis, so I had to adjust the code which generates the file names from 1. a JSON dataset and 2. from the actual Unicode code points.
- Now emojis work — except for a part where another library handles text. It doesn't detect Unicode 17 emojis and reports them back as string fragment.
And that's when I decided to stop giving a fuck.
I swear the software industry chose to handle emojis in the most annoying way possible. Why do I have to bother with code points and add a special code path to render them as images? Why can't projects just use a font which contains the latest emojis and let the OS/browser handle the rest? This way, it wouldn't even matter if my font gets out of date because then the OS font would be used.
But noooooo, emojis have to be special little snowflakes
Volpeon 