News for hackers. Stuff that matters.
Re:Input: Fonts for Code by Stratoscope on Saturday January 12, 2019 @04:40PM (#18893431)
> 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 by ztjio on Saturday January 12, 2019 @05:56PM (#18893803)
Reasons: I haven't found a proportional code font I like very much and, more importantly, many—MANY—existing code files include text arranged with the expectation of monospace fonts and if you use proportional, they become a mess.
Re:Input: Fonts for Code by samatman on Saturday January 12, 2019 @10:45PM (#18894915)
Agreed.

All respect to those who like proportional fonts, to each their own, but I think of code as a 2d grid.

Same reason I use syntax highlighting: color is another dimension that helps me see what I’m doing. This is particularly notable in Lisps, where turning on rainbow parens can be like switching on a light switch, immediately helping me understand the shape of the forms.

Re:Input: Fonts for Code by yellowbuilding on Monday January 14, 2019 @07:31AM (#18902496)
Inconsolata