When comparing Iosevka 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 Iosevka is ranked 6th. 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 Readable
Iosevka is very clear and legible on all displays and in all sizes.
Pro Narrow
Narrow character width uses horizontal screen space more efficiently.
Pro Large number of weights
This font comes in seven different weights, ranging from thin and extra-light to heavy.
Pro Great customizability
There is full customization of styles and variants in Iosevka.
Pro Support for Cyrillic and Greek letters
Iosevka is quite flexible in that it supports Cyrillic and Greek letters.
Pro Free and open source
Iosevka is free and open source.
Pro Powerline support
Includes characters for supporting Powerline/Airline for terminals and terminal editors.
Pro Ligature characters look great
Few fonts have a good ligation feature. Ligature characters (such as æ or the German ß) are supported in Iosevka and look just as you'd expect them to.
Pro Several styles available
Many of the common styles are available, including Sans Serif and Slab Serif with normal, bold, italic, and bold italic styles.
Pro IPA Support
IPA is a system containing the sounds of spoken language and includes speech qualities such as intonation.
Pro Easy on user's eyes
Due to it being readable on all types of displays, Iosevka isn't hard on the user's eyes.
Pro Well-maintained
The developer is active and responds to user questions and issues.
Pro Good CJK compatibility
Iosevka integrates CJK characters well, those being characters of the Chinese, Japanese, Korean, and occasionally Vietnamese languages.
Pro Also variant with tiny serifs available ("Slab")
For better reading longer texts.
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 Too narrow
Con Must do a custom build to get all ligatures
Con Fewer ligatures than other fonts
Iosevka has a nice ligation set, but it doesn't have as many ligatures as fonts like Hasklig, Monoid, or Pragmata Pro.
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.
