When comparing Fira Code vs MonoLisa, the Slant community recommends Fira Code for most people. In the question“What are the best programming fonts?” Fira Code is ranked 1st while MonoLisa is ranked 54th. 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
Ranked in these QuestionsQuestion Ranking
Pros
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.
Pro Customizable OpenType features downloads
The website offers customizable downloads for editors that don't support OpenType features natively.
Pro Script variant
It comes with script variant for italics.
Pro Ligatures
The typeface supports over 120 optionally enabled ligatures for common coding tasks.
Pro Italics
The typeface comes with an italic version.
Pro Space
Space used by the characters has been carefully balanced to keep them light to read.
Pro Reading flow
The characters have been designed to flow into each other so that the font feels easy to read.
Pro Distinction
Specific care has been put to make programming characters such as 1, i, and l or O or 0 easy to tell apart.
Pro Wider than usual
As it's wider, this means there's more space for designing characters like "m".
Cons
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.
Con Not free
This font requires a purchase in order to be used. The cheapest version ('Basic') is 60 dollars. There is a free trial, though.
Con Wider than usual
As it's wider, this means a short adjustment period may be required. If you have a limited amount of horizontal space, the wider glyphs may be problematic as well.