zlacker

>>nullch+(OP)
To all the people complaining about how they don't like ligatures:

Nobody cares. If you don't like them, then don't use them. They are optional.

Lots of people like them. Let people like things.

>>amake+Qv1
Ligatures make code harder to read and harder to edit. It's not just personal preference, it's the science of usability. When I press backspace or cursor keys, I expect one glyph to be erased, not who-knows-how-many (half?!).

Authors of content and programs with ligatures-by-default subject their readers and users to the penalty of ligatures.

Some people like pain, but that doesn't mean we need pain switches on everything with pain set to on by default.

>>cosmot+2R1
> When I press backspace or cursor keys, I expect one glyph to be erased, not who-knows-how-many.

That's you, and not very generalizable. Many people edit on sites with ligatures and many people edit non-Latin text where isolated, non-ligatured text is wrong (Arabic, some Indic scripts, Han characters, Japanese katakana).

Me personally, with respect to code, I pretty much think in terms of tokens: to remove the `==`, I backspace twice, rather than that to remove the `==`, I remove `=` and then the other `=`, and each requires one backspace.