I mean, I certainly wouldn’t give someone else shit for using ligatures, but personally, I don’t like them, because:
they break with monospacedness. Everything is in a nice grid and you’ve randomly got these character combinations that needlessly stick out.
they sometimes happen in places where they really shouldn’t.
they hide what the actual characters are. Especially, if go to edit that code, my brain will really struggle for a split-second when there’s a ‘≠’, then I delete one character and rather than the whole thing disappearing, I’m left with a ‘!’.
Sure, I could get used to it. But it being more readable is not even true for me, because the thing I got used to instead, is that != is the unequals-operator. I see that much more often than ≠.
For monospace fonts? I’ve heard of such research for proportional fonts, where ligatures definitely make sense to me. But yeah, I wouldn’t assume such research to automatically translate to monospace.
Ligatures are great. Don’t use them if you don’t like them, but don’t try to shame people for having different preferences.
The biggest exception to using ligatures is in documentation. I believe Kotlin used (uses?) ligatures in some of its documentation, leaving the reader to figure out if they actually need to type ≠ or if != will suffice. Not a great move, even if the IDE will render the ligatures just fine!
Ligatures 🤢🤮🤮
What’s wrong with Ligatures? It makes reading code a bit more tolerable.
I mean, I certainly wouldn’t give someone else shit for using ligatures, but personally, I don’t like them, because:
Do you also get surprised when you backspace a tab and suddenly it removes more whitespace than 1 characters worth?
Or did you learn it fast and really never think about it?
I think it’s more a “getting used to” thing, that once learned, you don’t think about, but it makes things more readable.
Sure, I could get used to it. But it being more readable is not even true for me, because the thing I got used to instead, is that
!=is the unequals-operator. I see that much more often than≠.Studies show that ligatures improve readability, but I acknowledge that it’s likely untrue for outliers.
For monospace fonts? I’ve heard of such research for proportional fonts, where ligatures definitely make sense to me. But yeah, I wouldn’t assume such research to automatically translate to monospace.
The IDEs I’ve used had the ligatures be of the same character width as the original operator.
You’re brave (I don’t agree)
I fucking hate that
Ifstyle.I mean, we read code more than we write it. You just vomitted over something that increases readability. Maybe a time for a rethink?
Ligatures are great. Don’t use them if you don’t like them, but don’t try to shame people for having different preferences.
The biggest exception to using ligatures is in documentation. I believe Kotlin used (uses?) ligatures in some of its documentation, leaving the reader to figure out if they actually need to type ≠ or if != will suffice. Not a great move, even if the IDE will render the ligatures just fine!