Also ligatures are optional, you aren't affected if you don't like the feature.
I guess I'm surprised that such a crucial feature isn't standard in everything if you can't even properly display a common language like Arabic without it.
Some prefer text to be seen as it was meant to be, so that === ugliness that can't be fixed at the source due to bad unicode support can at least be fixed at the output
But on the other hand, while I totally understand why https://sw.kovidgoyal.net/kitty/faq/#i-get-errors-about-the-... exists, it's quite annoying to handle that, as we often take this bit for granted.
It makes sense from a tech pov, but not from a product one. It's a choice and I respect that. It didn't prevent me to use Kitty for years.
My other problem was having TERMINFO available on remote servers. I’m not about to start installing alternative terminal emulators in prod, and while there is a workaround to losing control characters, IIRC it’s a pain.