Live data from Hacker News

Input: Fonts for Code

input.fontbureau.com

71–80 of 136 posts

Re: Input: Fonts for Code

#72
post #55

Earlier quoted context omitted.

Iosevka for me, you can custom build it with the letter designs you want, it supports ligatures and it's condensed without been cramped (also has Term, non-term and Slab variants in the same build). It's replaced my mono font everywhere , Fira Code is lovely but it feels way too wide once you've used Iosevka. The only font that comes close is Pragmata Pro but that's not free. https://raw.githubusercontent.com/be5invi…

I will chime in as another huge Iosevka fan. I have never really liked any of the other popular coding fonts and it really comes down to one thing: They are all stupid sans-serif fonts. I have found, ever since displays grew out of the garbage 100 dpi age, that serif fonts are vastly more enjoyable to look at and easier to quickly visually discern. As a result, Iosevka Slab is basically the only code-optimized font I…

My reasons are identical to yours, I also use the Slab version since my 'worst' screens are 2560x1440@24" it's just lovely on Linux.

Re: Input: Fonts for Code

#75
post #35

Yet to find something that suits me better than Fira Code. It's a decently good-looking font with ligatures . I'm a sucker for ligatures.

I used Fira because I felt the same about ligatures, until I found Hasklig. It has similar ligatures, but the overall font is better imo. https://github.com/i-tu/Hasklig

same, Hasklig is my favorite, it's just like Fira only better

Re: Input: Fonts for Code

#76
post #49

Yet to find something that suits me better than Fira Code. It's a decently good-looking font with ligatures . I'm a sucker for ligatures.

I loved Fira Code as well but it was love at first sight with IBM Plex https://www.ibm.com/plex/

Checked the website - looks like the zero isn't slashed, and I've spent too much time chasing down errors caused by oh's as zeros.

Re: Input: Fonts for Code

#79
post #55

Earlier quoted context omitted.

Iosevka for me, you can custom build it with the letter designs you want, it supports ligatures and it's condensed without been cramped (also has Term, non-term and Slab variants in the same build). It's replaced my mono font everywhere , Fira Code is lovely but it feels way too wide once you've used Iosevka. The only font that comes close is Pragmata Pro but that's not free. https://raw.githubusercontent.com/be5invi…

I will chime in as another huge Iosevka fan. I have never really liked any of the other popular coding fonts and it really comes down to one thing: They are all stupid sans-serif fonts. I have found, ever since displays grew out of the garbage 100 dpi age, that serif fonts are vastly more enjoyable to look at and easier to quickly visually discern. As a result, Iosevka Slab is basically the only code-optimized font I…

> Monospace is already such an awful layout for readability...

So why code in a monospaced font then? There's no rule that says you have to write code in a monospaced font. I've used proportional fonts for many years, and almost every programmer's editor supports them.

I'm currently using a slightly modified version of Trebuchet MS (I replaced the tilde with a better one). Another example is Input Sans, one of the three fonts today's thread is about.

If you like proportional fonts, go for it!

Re: Input: Fonts for Code

#80
I'm a font-aholic and reading Hacker News, I get the impression I'm not the only one.

My first adventure down the font hole started with Bit Stream Vera Sans Mono followed by Source Code Pro. Stuck with Source Code Pro for many years and even today, not sure any other aliased font looks and works as well as Source Code Pro at almost every size, from the smallest onward. It just looks clean to me.

After reading on here how great it was, switched to Fira Code for a while. It was nice, but never blew me away. The ligatures were a nice change I guess.

Then I tried out Iosevka and was happy. Kept using it for a while.

Then it was Input Mono, again happy and used it for a while.

I was later introduced to Operator Mono and thought I had found code font bliss (pay).

Ended up going back to SF Mono (I'm on macOS) and feel content. Finally. Again. I don't think I'm switching anymore. I might try for a day or a few minutes something else, but I can't see myself sticking with it like SF Mono. It will have to blow my mind.

As an aside, I love no antialias Monaco at about 10 pt on hi dpi/retina displays (MacBook Pro 2017 and LG 5k with non-decimal scale, e.g. 2x). Something about it seems perfect to me. It usually seems to require special configuration and sometimes is difficult or not supported at all in many tools and editors, so I have stuck with SF Mono, typically 11 pt or 13 pt depending on the display and time of day and how much sleep I got.

Post reply on HN