I have been going back and forth between Luxi Mono (serif monospace fonts are rare but look great on high-resolution monitors) and Hack (like Helvetica, it has virtually no personality and thus fits well everywhere). Everything else I've seen has looked... weird or off somehow. But this is one of the first alternatives I'm entertaining the idea of trying.
My main concern is that the tall glyphs for less than < and greater than > will disambiguate badly with actual Unicode left 〈 and right angle brackets 〉.
Nice work. I unfortunately wouldn't be able to use it for programming because I find the parenthesis and square bracket look too similar, and it would definitely increase extraneous cognitive load.
Funny, I found this font last week on the programming fonts website before it blew up. Was using IoskeleyMono before, and think this is my endgame for now! Amazing readable font.
Brilliant project. The face looks good. The code looks good. It’s nice to see it in Python too. I don’t especially love the language but I have a great fondness for seeing life things codified with a standard API in a typed (or at least, type-able) language. Needing to draw an “A” in something without having to pull in font libraries (that is to say passing a compatible draw context to this project’s LowercaseAGlyph.draw) sounds nice.
Y'know, I didn't think anything was gonna pull me away from Iosevka but... here we are. Gonna give this a real go. Helping its case is that it looks a bit like Berkeley Mono.
`Only two minimal ligatures are exposed with "->" and "=>".`
I like that, I usually have ligatures turned off, because I don't like all of them, especially the ones for == or ===. (Otoh I do like != ligatures...) but I do like the arrows.
This is probably were somebody tells me how easy it is to configure singular ligatures on a font and I'll facepalm in embarrassment for never finding out.
I hate all of them with a passion, because they look like a glyph (i.e. "something you can erase with a single backspace") but aren't. This confuses me first, and annoys me second. "Just because we could" doesn't mean that we should.
Imagine having to use Backspace twice to erase e.g. Ö or Ñ, or being able to place your cursor halfway inside Æ.
Thanks for mentioning it! First time I heard about Commit Mono. The first paragraph already had me wondering how a monospace font can read this well.
Turns out it has smart kerning, ie. character positions are subtly adjusted to compensate for different character widths. For example, i is narrow and m is wide. That causes words like "commit" to look bad in standard monospace fonts. The m's in the middle are very densely spaced and there are wide gaps around the i.
I'll be testing Commit Mono in my editors. Maybe it will even make me switch SilverBullet back to a monospace config.
My main concern is that the tall glyphs for less than < and greater than > will disambiguate badly with actual Unicode left 〈 and right angle brackets 〉.
LE: Ok, so it's a little more different that JetBrains Mono as this comparison shows https://claude.ai/artifact/HPiALZ7AZ2f5FxSZtcTdNa
And who isn't?
Squints - m is too weird - tab closed :)
Bitch please… https://github.com/rbanffy/3270font.
https://github.com/tywr/Nordwand-Mono/blob/main/src/glyphs/n...
[1]: https://usgraphics.com/products/berkeley-mono
https://github.com/shytikov/pragmasevka
https://github.com/ahatem/IoskeleyMono
Pdf preview doesn't work on GitHub.
I like that, I usually have ligatures turned off, because I don't like all of them, especially the ones for == or ===. (Otoh I do like != ligatures...) but I do like the arrows.
This is probably were somebody tells me how easy it is to configure singular ligatures on a font and I'll facepalm in embarrassment for never finding out.
[1] https://github.com/fontforge/fontforge
I hate all of them with a passion, because they look like a glyph (i.e. "something you can erase with a single backspace") but aren't. This confuses me first, and annoys me second. "Just because we could" doesn't mean that we should.
Imagine having to use Backspace twice to erase e.g. Ö or Ñ, or being able to place your cursor halfway inside Æ.
Turns out it has smart kerning, ie. character positions are subtly adjusted to compensate for different character widths. For example, i is narrow and m is wide. That causes words like "commit" to look bad in standard monospace fonts. The m's in the middle are very densely spaced and there are wide gaps around the i.
I'll be testing Commit Mono in my editors. Maybe it will even make me switch SilverBullet back to a monospace config.