3 ms·

I agree the ligatures are a bad idea, and I use a ligature font in my editor. I quite like ligatures, I find they moderately enhance readability, but you need t

I agree the ligatures are a bad idea, and I use a ligature font in my editor. I quite like ligatures, I find they moderately enhance readability, but you need to know exactly what they are for it to be useful: readability can't come at the cost of precision in a code sample.

oefrha 6y ago
I'm actually far less bothered by programming ligatures than cursive font for comments. It just so happens that Operator Mono bundles these unconventional features together, so I kind of lumped them together. But yeah, using ligatures in code that’s meant to be shared isn’t a great idea.
- enriquto 6y ago
  Cursive font is annoying, but bold fonts make my blood rage.
wasureru 6y ago
In terms of fonts, what’s the difference between readability and precision?
- oefrha 6y ago
  Readability of programming ligatures is very different for people who are familiar with the language/font, and people who aren't. For instance, look at the list of ligatures for Fira Code[1] and without referencing the monospace counterparts on the right, tell me if you can tell how to reproduce each one without a lot of guesswork. [1] https://github.com/tonsky/FiraCode https://github.com/tonsky/FiraCode
- wyattpeak 6y ago
  In the sense I'm using them, readability is the ability to scan as quickly as possible, precision is the ability for someone unfamiliar with the font to be able to reproduce what they see. I find ligatures more readable because for example I read the => ligature faster than the two-character equivalent. I find it less precise because someone who sees the ligature may not be clear what it's supposed to be (when I first saw a ligature font, I thought it was a unicode character).
  - toastal 6y ago
    ⇒, the Unicode symbol, is supported in PureScript and Agda out of the box and is supported in Haskell with UnicodeSyntax extension. Personally, I find the ligatures more confusing than support for the actual Unicode symbols (albeit they can be more cumbersome to type if your editor doesn’t help, i.e. ctrl+k "=>" in Vim). Every time someone uses Fira Code in a presentation someone in the audience always has to ask and now you have to go down a rabbit hole of explaining what ligatures even are.
    - matheusmoreira 6y ago
      > albeit they can be more cumbersome to type if your editor doesn’t help, i.e. ctrl+k "=>" in Vim I wonder why physical keyboards lack unicode support. Virtual keyboards often have great support for this. Older keyboards could also input a lot of symbols: https://upload.wikimedia.org/wikipedia/commons/4/47/Space-cadet.jpg https://upload.wikimedia.org/wikipedia/commons/4/47/Space-ca...
      - toastal 6y ago
        Could be an issue with agreeing on a standard. But also, the average user would rather have emojis on a keyboard before various math symbols (and, outside work, I'd feel the same).

oefrha 6y ago

I'm actually far less bothered by programming ligatures than cursive font for comments. It just so happens that Operator Mono bundles these unconventional features together, so I kind of lumped them together. But yeah, using ligatures in code that’s meant to be shared isn’t a great idea.

enriquto 6y ago
Cursive font is annoying, but bold fonts make my blood rage.

wasureru 6y ago

In terms of fonts, what’s the difference between readability and precision?

oefrha 6y ago
Readability of programming ligatures is very different for people who are familiar with the language/font, and people who aren't. For instance, look at the list of ligatures for Fira Code[1] and without referencing the monospace counterparts on the right, tell me if you can tell how to reproduce each one without a lot of guesswork. [1] https://github.com/tonsky/FiraCode https://github.com/tonsky/FiraCode
wyattpeak 6y ago
In the sense I'm using them, readability is the ability to scan as quickly as possible, precision is the ability for someone unfamiliar with the font to be able to reproduce what they see. I find ligatures more readable because for example I read the => ligature faster than the two-character equivalent. I find it less precise because someone who sees the ligature may not be clear what it's supposed to be (when I first saw a ligature font, I thought it was a unicode character).
- toastal 6y ago
  ⇒, the Unicode symbol, is supported in PureScript and Agda out of the box and is supported in Haskell with UnicodeSyntax extension. Personally, I find the ligatures more confusing than support for the actual Unicode symbols (albeit they can be more cumbersome to type if your editor doesn’t help, i.e. ctrl+k "=>" in Vim). Every time someone uses Fira Code in a presentation someone in the audience always has to ask and now you have to go down a rabbit hole of explaining what ligatures even are.
  - matheusmoreira 6y ago
    > albeit they can be more cumbersome to type if your editor doesn’t help, i.e. ctrl+k "=>" in Vim I wonder why physical keyboards lack unicode support. Virtual keyboards often have great support for this. Older keyboards could also input a lot of symbols: https://upload.wikimedia.org/wikipedia/commons/4/47/Space-cadet.jpg https://upload.wikimedia.org/wikipedia/commons/4/47/Space-ca...
    - toastal 6y ago
      Could be an issue with agreeing on a standard. But also, the average user would rather have emojis on a keyboard before various math symbols (and, outside work, I'd feel the same).