91–100 of 342 posts
Earlier quoted context omitted.
Can you easily differenciate between == and === with ligatures ? That's one thing that holds me back to trying ligatures.
Of course. A `==` is two characters long, while `===` is three characters long. Also, with the font I use (Fire Code) the `===` ligature has three lines, making it even easier to distinguish.
One thing I noticed: I really want a different font for my terminal than for my editor – for the terminal I went for DejaVu Sans Mono, it's clean but still has some character, especially the dotted 0.
Earlier quoted context omitted.
This looks really nice, too bad it doesn't (and never will) support ligatures. I understand the point the author is trying to make about ligatures in the separate blog post, but boy do I love my ligatures when programming.
Can you easily differenciate between == and === with ligatures ? That's one thing that holds me back to trying ligatures.
More and more often, I see ligatures being used on such fonts. E.g. === or != are combined in a visually single character. Personally, I don't like that at all as I think it makes code less readable. It is probably something that you can get used to. But what exactly is the appeal of it anyway?
Well I guess the idea is that the ligatures represent the concepts that the combination of symbols are trying to represent. Also it looks pretty If you're staring a text editor for 8+ hours a day, it is important what you are staring at is pleasing to you.
So, as long as the font I'm using doesn't actively impair legibility, which is a pretty low baseline, it doesn't really matter - and in any case, if it's a visual aesthetic I want, I'll go do it in Illustrator where I can actually have precise control over every aspect of that aesthetic, instead of forcing my programming environment to double as an installation art piece.
(DejaVu Sans Mono, in case anyone cares, or Menlo on Apple hardware since it doesn't want installing. Haven't changed it in what must be close to a couple decades by now; somebody sneakernetted me a copy of Vera Sans Mono in my earliest days of moving up from the helpdesk and I never looked back. Doesn't changing fonts impose a cognitive overhead of its own for a while?)
...all of which is to say I favor brutalism, I guess.
More and more often, I see ligatures being used on such fonts. E.g. === or != are combined in a visually single character. Personally, I don't like that at all as I think it makes code less readable. It is probably something that you can get used to. But what exactly is the appeal of it anyway?
> But what exactly is the appeal of it anyway? To answer this question you probably need to start broader with: why do ligatures exist in fonts at all? Then see if that applies to programming. There's various accounts of the "reasons" ligatures came to be, but of the few I've seen all would (imo) apply equally to code as to language. The obvious one is pure aesthetic preference, but another is that ligatures came abo…
Earlier quoted context omitted.
Of course. A `==` is two characters long, while `===` is three characters long. Also, with the font I use (Fire Code) the `===` ligature has three lines, making it even easier to distinguish.
I just had a look at Fire Code. How do you distinguish -> with ligatures from → (an Unicode arrow)?
This needs an option to adjust the font size used with samples. Lots of fonts show some really weird artifacts in smaller sizes. Also, the list needs Dina [1] in its TTF version [2] [1] https://www.dcmembers.com/jibsen/download/61/ [2] https://chrisrickard.blogspot.com/2010/05/geenatcom-dina-ttf...
Earlier quoted context omitted.
Of course. A `==` is two characters long, while `===` is three characters long. Also, with the font I use (Fire Code) the `===` ligature has three lines, making it even easier to distinguish.
I just had a look at Fire Code. How do you distinguish -> with ligatures from → (an Unicode arrow)?
More and more often, I see ligatures being used on such fonts. E.g. === or != are combined in a visually single character. Personally, I don't like that at all as I think it makes code less readable. It is probably something that you can get used to. But what exactly is the appeal of it anyway?