Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing 6x13 fixed 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 6x13 fixed is ranked 37th. 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 Well designed
6x13 fixed is the apex of bitmap fonts. It has a nice, defined character set and great proportions for quantity of text onscreen, making for excellent readability. It is aesthetically pleasing for a bitmap font and has been deservedly termed 'classic'.
Pro Legible at small sizes
At a small text size, each character has a limited resolution. A character size of 6x13 pixels means only 78 pixels per character. Modern fonts are designed to be scalable and are less legible at these small sizes. Using bitmap fonts increases legibility by eliminating scaling and sub-pixel aliasing artifacts. Some scalable fonts include "ppems" embedded bitmaps for this reason.
Pro Available on every X server
6x13 is the classic fixed monospace bitmap font that is expected to be available on every X server. It is part of the misc-fixed family. These fonts were handcrafted for readability in a terminal.
Pro Widely available
It is distributed alongside the X Window System.
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 Doesn't have a slashed zero
The absence of non-slashed zeroes makes it harder to distinguish "0" from the letter "O".
Con Extremely small on high-DPI screens
While it is crafted for a screen where the pixels are visible, bitmap fonts do not work well on high-DPI screens as they do not scale too well.
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.
