5 ms·
Following æsthetic at the cost of function is a complaint I’d make of Fira Code, not JetBrains Mono (disregarding ligatures, which both overdo): Fira Code’s r g
by chrismorgan 5y ago
Following æsthetic at the cost of function is a complaint I’d make of Fira Code, not JetBrains Mono (disregarding ligatures, which both overdo): Fira Code’s r glyph is lousy, its & poor for code where immediately followed sans whitespace by letters (common for reference syntax in C-family languages; it’s much too similar to a letter, especially given the high ex height), and its ff ligation (two columns → one) downright idiotic.
- minimaxir 5y agoFair. At the least, some of those examples have variants that can be manually enabled: https://github.com/tonsky/FiraCode/blob/master/extras/character_variants.png https://github.com/tonsky/FiraCode/blob/master/extras/charac...
- chrismorgan 5y agoActually, I must amend what I said: I was talking about Fira Mono rather than Fira Code. Fira Code fixes the r glyph (its default r glyph is excellent and its alternative perfectly respectable, still having narrowed the base line), and offers a better ampersand as an alternative. Dunno about the f ligations (ff, fi, &c.), hopefully they ditched that madness (even if they’re opt-in discretionary ligatures in Fira Mono—they just have absolutely no place in a monospaced font, dlig or no dlig).
- chrismorgan 5y agoIt seems like I might have to make another amendment as I just came across something labelled Fira Mono that also seems to have the fixed r glyph. I’m throwing in the towel, there are too many things called Fira Mono and Fira Code and I can’t find any one sound canonical source; some seem to say there are a bunch of changes between the two, others seem to say it’s only a different line-height; did they perhaps start out more different but get mostly merged back? I give up. All I know is that places like bugzilla.mozilla.org and crates.io use bad versions of some Fira monospace font.