When comparing Fira Code vs SF Mono, the Slant community recommends Fira Code for most people. In the question“What are the best programming fonts?” Fira Code is ranked 1st while SF Mono is ranked 39th. 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 Good editor support
A list of supported editors and terminals can be found here.
Pro Supports retina displays
Fira Coda supports high pixel density retina displays.
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 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 Has a slashed zero
New style since February 2018.
Pro Clear and dis·tin·guish·a·ble
Code is very readable at both big and small sizes.
Pro Beautiful with high pixel density
Cons
Con Dotted zero is less readable than slashed zero
FiraCode uses dotted zero instead of slashed zero which is less readable.
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 Needs support for ligatures
It can't work in plain terminal, must have built in support for ligatures in editor
Con Lowercase 'r' looks off
See issue mozilla/Fira#49
Con Ligatures like == and === are harder to tell apart than they should be
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 Ligatures lump some characters together and make them hard to read
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 No Sublime Text support
Not the font's fault but even the latest Sublime Text builds (e.g. 3126) don't support ligatures.
Con Slightly difficult to use outside of Xcode, Terminal, or Console
The typeface isn't available in Font Book, etc. unless the user imports the files embedded in the apps above.
Con Apple is locking down this font
It's not open in any sense of the word. It even gives warnings if you try to rip it out of the Terminal.app or Xcode bundles. Obviously, Apple only wants it on their tools. This is such a shame. It should work in other editors, too. It's a beautiful font. Apple open sourced swift, why can't they be open with a monospace font?