Though it turns out that VS Code default (Droid Sans Mono) is (to my eye) basically identical to my winner (Roboto Mono), so the exercise was mostly academic.
- An ELO-based version with many more variables, so that I can open the site from time to time and find more nice fonts
- Some global stats
- Not losing the leaderboard after reloading
- Spline Sans Mono
(FWIW, I just did the codingfont bracket and got Source Code Pro, which I've used in the past, along with Iosevka and Commit Mono)
Chrome (assuming you're using Chrome) draws it a specific way. This does not match how Freetype (using typical tuning) or DirectWrite draws it. Chrome's choices in font renderer tuning and blending makes it kind of split the difference between Windows-style and OSX-style, and isn't native to either.
What it should be doing is showing you lossless screenshots of actual in-app renders at different sizes. Some in Chrome (to represent the Electron apps), some in DirectWrite, some in OSX post-Retina, etc.
Some fonts look amazing at larger sizes, but are unreadable at smaller ones. Some perform exceptionally well at smaller sizes. Some look great on every font renderer but OSX's, but some only look right on OSX and look bad everywhere else.
I've sorta played this game with myself, in a semi-objective way: take a bunch of fonts, ignore the subjective art nature of them, and throw them at a bunch of common renderers and see what the optimal size is, and then sort by smallest legible size.
If we define Fira Code, the most popular code font out there, as the bare minimum, 8 of the ones I tested beat it, while 17 were worse.
https://github.com/Diablo-D3/dotfiles/blob/master/fontsizes....
At the same time, it would be wonderful if window sizes were more consistent (now things are obstructed, with scrolling, etc). And I would love to download the ranking graph!
On the game/bracket: it narrowed me down to Noto Sans Mono and I'm honestly not surprised, it's one of the few fonts that comes with my operating system that I find acceptable.
That being said, what I actually have my terminal and Emacs set to is “AcPlus IBM VGA 8x16” from https://int10h.org/oldschool-pc-fonts/. I've always been fond of the VGA font and it tickles all the right usability marks for me.
But I prefer (and use) PragmataPro (not free) and it is not part of the test, sadly.
There's a vector version[2] now too!
[2]: https://github.com/bluescan/proggyfonts/tree/master/ProggyVe...
* https://news.ycombinator.com/item?id=42554715
Results: Roboto Mono !
I'm using Liberation Mono, and it's missing :( i got PT Mono though.
It would be nice if it showed you 1st, 2nd, semi-finalist, quarter-finalist...
It would also be nice to see progress of some kind, a few minutes in I was wondering if I was near completion or just getting started.
[ MAPLE MONO ]
(on Github https://github.com/subframe7536/Maple-font). It has amazing readability, looks nice, is compatible with NF if you use that. I received compliments from people looking over my shoulder for my f'ing font?! Huge shoutout to subframe7536 ^^
What I noticed while playing was that when fonts are similar, I really pay attention to the rendering of "m" and "r". When they look off, the whole font looks off to me.
For coding I much prefer fonts that are bold and easier to read. Who actually likes these whimsical cursive looking comments or super thin looking fonts?
I ended up with "Roboto Mono" btw.
Would be nice to be able to play it with my own fonts because some got eliminated purely because 0 (zero) looked like O (letter). Fira Code was a winner only because there weren't paid fonts that I use.
This way I can focus on coding and less on tweaking my environment.
https://www.comicbookfonts.com/Code-Monkey-Variable-font-p/b...
Unfortunately plus signs display as blank spaces in the test drive. Oh well.
Also, about half of these fonts look utterly unsuitable for coding to me. Nobody really needs serifs and loopy l's in a coding font, surely?
It's hidden behind the menu button on mobile.
It's so good. Perfect even. And they have a really neat customization tool.
I've been using it for a few years now and they actually still occasionally release a new version of it. Haven't gotten tired of it yet.
The only complaint I have about it is that I had to do a hacky workaround to get my Nix setups to pull it in since it's proprietary.
I even forked their "Machine Report" tool (which presumes Debian) to make it work on Linux/NixOS by applying a "polyfill": https://github.com/pmarreck/usgc-machine-report-nixos-editio...
I wonder if it's Stockholm syndrome or if I really do prefer it. It's a totally fine font, I've never felt the need to change it. All the default open source mono fonts seem completely adequate I suppose.
Anecdotal solely to me, very unnerving and even with formatting marks enabled makes me feel uneasy seeing a space without a space formatting mark.
I came from Fira Code to JetBrains Mono to MonoLisa (several years each) then finally settled on Berkeley Mono and refuse to use anything else!
https://github.com/githubnext/monaspace/blob/main/docs/Textu...
That said, these days I almost exclusively use Input Mono [0], specifically the "Narrow" variety. With an occasional sprinkling of either Iosevka Fixed or PragmataPro Mono.
I made myself my own pixel-perfect perfect font, more than 10 years ago. I simply copy it from one system to the next one when I upgrade (either the machine or the OS).
It's basically a modified pixel-perfect Terminus font, but with some elements mixed from an old pixel-perfect Monaco font and some modification of mine.
Something I cannot live without is a tall pipe symbol. And my pipe symbol must have a hole in it in the middle (and it cannot be mistaken for an exclamation mark).
I've got the following as a quick test. The reason for a,b,c,e is to verify that <>,{},[], etc. all perfectly align vertically.
Everything is correct, to the pixel.
I don't believe in anti-aliasing for a coding font, not even on a retina display, and I love my 3840x1600 pixels 38" monitor and it's pixel size is perfect to me.
RA $|-sSTtf the little fortran
gqy z2Z s5S 8B CG6 DO uv ;; these should look different (8 / B is difficult to get right)
a!?aA! [a]
b!?b {b}
c?!d (c)
c?c <e>
c!c
if ( a && b || c & d) { [0x88, 0x42, 0xFA, 0xdeadcafebabe]; }
*if ( a && b || c & d) { [0x88, 0x42, 0xFA, 0xdeadcafebabe]; }*
;; found somewhere
lnt foob1x -= {(0)} "'foo'bar";
int foOblx == ((0)) 'foo`bar`' `"':
|nt f0obIx += {{o}} '"O08! LIl1i!!| 7?
the lowercase 's' has a shorter upper bar and the lowercase 'l' is stylised.The thing is: I obsessed for days, creating my own pixel-perfect font. And I don't need to tweak it anymore: it's perfect (to me, YMMV) and I use it ever since.
Can't share it as I reused both Terminus and chars from Monaco.
FWIW I had more than 10/10 eyesight (once you get at 10, there are additional tests) and in my entire life I've never seen one person beat me at the "read sign on the highway". Pixel-perfect font, no AA, custom made font for me. YMMV. Haters gonna hate.
> I don't believe in anti-aliasing for a coding font, not even on a retina display
This is a very good point. As resolution increases, antialiased fonts become less ugly, but also less necessary. Thus at no resolution they make any sense; but they look ridiculous for different reasons.
Plex is a beautiful font, and one of the few corporate fonts that I actually think works, while being recognizable as being IBM.