Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Inconsolata-g vs Fira Code, the Slant community recommends Fira Code for most people. In the question“What are the best programming fonts?” Fira Code is ranked 1st while Inconsolata-g is ranked 5th. The most important reason people chose Fira Code is:
This is particularly beneficial for those who wish to use combined letters such as "æ" and other diphthongs. But when it comes to programming, the ability to scan through your code is improved with ligatures for equality, arrow functions, and more.
Specs
Question Ranking
Pros
Pro Free and open source
Inconsolata-g has been released under the SIL Open Font License 1.1.
Pro Fixes clashing of similar characters
Inconsolata-g is a variant of the popular Inconsolata that fixes the similarity between "1" [one] and the "l" [lowercase ell].
Pro Great scalability
Inconsolata mantains its legibility even with small font sizes.
Pro Line height is a little larger than normal
This makes the lines feel less crowded which greatly helps readability.
Pro Has ligatures
This is particularly beneficial for those who wish to use combined letters such as "æ" and other diphthongs. But when it comes to programming, the ability to scan through your code is improved with ligatures for equality, arrow functions, and more.
Pro Supports retina displays
Fira Coda supports high pixel density retina displays.
Pro Characters look really nice
Some characters that look odd in other monospace fonts look very nice in Fira Code: @, a, 1, lower-case-L, Q, j, *
Pro Good editor support
A list of supported editors and terminals can be found here.
Pro Has a slashed zero
New style since February 2018.
Pro Frequent updates
The repository is frequently updated.
Pro Installs easily on Mac
Many ligature fonts on Github aren't "mac ready". This font comes pre-compiled and ready to install on Windows, Mac, and Linux.
Cons
Con No Italics
To improve contrast, italics are best used for comments.
Con () and {} are difficult to distinguish
The user may have difficulty distinguishing small size () and {} at a glance.
Con No pretty ligatures
Ligatures are nice-to-have in languages such as Swift.
Con Looks too small next to other fonts
Con Character widths are not consistent between regular and bold
Bold characters are not the same width as regular characters so the typeface is not consistently monospace.
Con Dotted zero
Dotted zero is less readable than slashed zero.
Con Looks significantly worse on Windows (ClearType)
Con Renders lines as dashes in TUI interfaces
Lines in items like midnight commander, the treeview in htop, tmux panes, the tree command, et al., have ugly dashed lines instead of straight lines with sharp corners.
Con Requires more work than Inconsolata to install on several OS's
Because Inconsolata is in the package managers for almost all open source OS's, it is much easier to install than Inconsolata-g in most cases.
Con The '@' Symbol is asymmetric
It's a style, but it would be nice if it would wrap and not just cover the top.
Con No true italic
Italic is just a slanted original, an Oblique. Looks ugly and is difficult on the eyes.
Con Noisy serif-like style harming the text clarity
Con Ligatures are nice-looking but harm clarity
Even though the font combines characters into ligatures, you still need to type the normal characters, and the ligatures make that difficult in many cases.
Con Ligatures like == and === are harder to tell apart than they should be
Con Too wide, too large line height
Con Too wide
Much wider than other fonts.
Con Ligatures lump some characters together and make them hard to read
Con Needs support for ligatures
It can't work in plain terminal, must have built in support for ligatures in editor.
Con No Sublime Text support
Not the font's fault but even the latest Sublime Text builds (e.g. 3126) don't support ligatures.
Con Ligatures break correlation between symbols on screen and the number of characters
This makes it easier to lose the grasp how long lines actually are.
Con Curly braces are not clear enough
Curly braches ("{" and "}") are not clear enough. They are too horizontally narrow, making them look almost like pipes ("|").
Con Bad 4 and r characters, dotted 0
WHY is r a serif?
Con Cannot enable alternative stylistic styles on Xcode
I've tried enabling some of the alternate stylistic styles using Xcode's Font picker, via the "Typography" screen. None of the stylistic styles I enable get reflected in Xcode's code editor, even if I restart Xcode from scratch. I'm not sure whether this is a limitation of Xcode, or of the font itself.
