On: Monospaced Programming Fonts with Ligatures

[masklinn]

Why would it be sarcastic? The triple bar is also the operator for logical equivalence, which I guess is where the font authors got it.

[gervase → masklinn]

I assume potential sarcasm would be related to the difficulty differentiating between similar symbols, based on length, with different lexicographic meanings.

For example, dash vs endash vs emdash, etc: ‒ – — ―

If those symbols were used in a programming language and had different meanings, differentiating quickly could be much more difficult than seeing the difference between -, --, ---, and so on at a glance.

[NoodleIncident → gervase]

But the point of the new triple-equals ligatures is that they're no longer only differentiated by length; they have three bars instead of two, as well.

[amk_ → gervase]

Just recorded this GIF of typing out a function with the added visual cues:

http://imgur.com/a/LQVV2

IMO it's comparable to a WYSIWYG equation editor vs looking at raw LaTeX - conceptual errors pop more.

[FireBeyond → amk_]

Also out of curiosity, what editor / plugins are those?

[amk_ → FireBeyond]

Just VSCode with the ESLint plugin and this theme: https://marketplace.visualstudio.com/items?itemName=jdinhlif...

[jstarks → amk_]

OT, but out of curiosity what did you use to record this?

[amk_ → jstarks]

I used https://getkap.co/

[masklinn → gervase]

> the difficulty differentiating between similar symbols, based on length, with different lexicographic meanings.

The very thing amk_ is praising is that this issue is fixed in both Fira and Monoid by the triple-equal being not just longer but represented using 3 horizontal bars rather than just 2.

[amk_ → masklinn]

exactly, and the !== != forms are also correspondingly adjusted