Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

In the past, we’ve had to decide between tiny monospace fonts or jagged edges. But today, modern operating systems do a great job of anti-aliasing, making monospace fonts look great at any size. It’s not 1990 anymore. Give your tired eyes a break and bump up that font size.

No, thanks. All the anti-aliased screenshots in his post look blurry and some make me outright cringe.

Also he missed my personal favorite: http://www.netalive.org/tinkering/triskweline/



I concur about the blurriness. It'll be a good day indeed when everyone has a 300dpi display and we can get rid of anti-aliased text for good. Anti-aliasing looks great for headlines at large point sizes, but for bulk text, that blurry look is bad for my reading speed, and a continual distraction, as well. I hate that about Linux, how hard it is to find a free font that looks good when hammered into the pixel grid, and it's nice to see some new ones from time to time.


That's a good-looking font, but I personally need a big visual distinction, like a slash or a dot, between O's and 0's. (I do like the distinction between l's and 1's, though - lots of fonts screw that up.)


Well, I think I would prefer a slashed zero for confidence, too, but can't say this has ever been an issue in my years of real world use.


That's why I said "I personally". :)


That font makes me cringe. It reminds me of when the screen resolution is too narrow, widening all text.


Same here. The letter-forms themselves look good, though. Maybe if the spacing between the letters were narrower? The kerning (that's what it's called, right?) seems unusually large, particularly for a fixed-width font.


Well, trisk is very legible for me at normal reading distance where e.g. proggy or profont feel too squeezed and slightly too small. But ultimately it's also a matter of taste, ofcourse.

Generally screenshots can hardly do programming fonts justice. You have to load them into your editor and try them out on familar code.

Most of the fonts showcased on that page look perfectly fine to me from the images. I only learned that I can't bear an anti-aliased font and about my various gripes with the other fixed contenders because I once went and tried all of them for at least a few hours each.


Agreed. Aside from a few major variables (fixed-width or variable-width, anti-aliased or no, weight), and ruling out fonts with obvious flaws like making 0 and O look too similar, it's largely a matter of taste.

I've found that some fonts look much better as light text on dark backgrounds, or vice-versa. I use terminus (http://shenani.gen.nz/~scott/img/terminus-sample.png), but something about it doesn't look right to me on a light background.


Indeed. I found the choice of font less critical on light backgrounds but that might be because I'm a white-on-black fanatic and can't bear a light background for long anyways - regardless of font.

But I, too, noticed the difference and I don't think it's just subjective. Black-on-white is generally easier on my eye in the short-term but for the long-term (e.g. coding sessions) I strongly prefer white-on-black because staring at a mostly white screen for extended periods of time makes me dizzy.


Yeah, I know some font rendering technology specifically draws dark-on-light-bkgnd differently from light-on-dark-bkgnd, though I can't recall where I've seen it, or the details ...




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: