Thanks, I hate it. My most recent update of IntelliJ turned this font on by default and I had to spend an hour trying to figure out what the font used to be. Mono looked squished to me - the intentional favoring of length over width made the whole editor look like I had an aspect ratio problem on my monitor. I appreciate trying to push the envelope and improve ergonomics, but I wish this would have been opt-in for up…
Interesting. It didn't do that for me. But, I had already specifically set my font. So, maybe it changed the previous default to this new font.
JetBrains Mono: A free and open-source typeface for developers
31–40 of 207 posts
Re: JetBrains Mono: A free and open-source typeface for developers
#32Re: JetBrains Mono: A free and open-source typeface for developers
#33The site design is nice but I found it a bit odd that they didn’t include many of the similar character like O, 0, 1, l, I. That is one of the first things I look for and one of the primary reasons I would choose a new font.
Re: JetBrains Mono: A free and open-source typeface for developers
#34It is an odd decision not to include Ukrainian in the list of supported languages, despite the fact that the font has all the necessary letters.
Re: JetBrains Mono: A free and open-source typeface for developers
#35I was disappointed that despite presenting the cookie banner as if it were a terminal, the options did not accept keyboard input [Y]es, I agree [N]o, thanks Ok on topic: I'm never sure what to think of these "developer" fonts that make use of ligatures for combinations like ==, >=, ->, =>, etc. On one hand they do look really nice, but I always can't help but feel it would actually make things just a little bit harde…
Emacs has a minor mode (prettify-symbols-mode, I think) that makes substitutions like these. I tried it for a couple of months, but decided that it wasn't for me.
But it did keep me entertained for a bit.
Re: JetBrains Mono: A free and open-source typeface for developers
#36That being said, fonts are very personal.
I compared it to PT Mono (Public Type, another open-source font) and have these observations:
- Ligatures in JB are beautiful. I'm still undecided whether I like them in my code but the aesthetic value is pleasing.
- Weight of JB Regular is heavier than PT.
- Italics are well designed.
- Character spacing is too wide. Words (eg. for identifiers) loose some of their shape and look more like a stream of disjoint characters. Subtle but going back and forth between the 2 fonts, this is the first thing that jumped out. That being said, this would probably benefit code that's rich in symbol characters.
All in all, I'm glad this font exists, it is beautiful. But for my own use, I will stick with my trusty PT Mono.
Re: JetBrains Mono: A free and open-source typeface for developers
#37It looks like this has the largest x-height of any typeface meant for developers (larger than even Fira Code). While there is research suggesting a large x-height increases readability, I'm wondering whether this doesn't push the x-height just a little too far. CamelCase words no longer stand out visually very easily -- I'm not sure how I feel about that.
Re: JetBrains Mono: A free and open-source typeface for developers
#38> 1. Increased height for a better reading experience
A high x-height is good for coding fonts, but this x-height is now too high. To my eye, this is now at the point where lowercase letters are getting harder to distinguish from uppercase letters at a glance, so instead of increasing legibility it's actually decreasing it now. There's a good reason most other coding fonts haven't gone this high.
> 2. The shape of ovals approaches that of rectangular symbols.
Again, this is a problem because it makes letterforms harder to distinguish. It's important that the right side of a "b" look very different from an "h"... but if you make the right side of the "b" very straight, they look more similar. The whole point of letterforms is to be easy to differentiate from each other, not to make them more similar.
> 3. JetBrains Mono’s typeface forms are simple and free from unnecessary details... The easier the forms, the faster the eye perceives them and the less effort the brain needs to process them.
Again, this is just factually false, or else all books would be printed in sans-serif body text instead of serif. The main reason serif fonts are used is that all their extra "details" make reading easier, not harder -- because the eye has more clues to differentiate letters. Now because of resolutions of screens, sans-serif is still sometimes a better choice on computer screens, but this makes distinctiveness of letterforms even more important, not less.
For example, they choose a single-story instead of double-story lowercase "g", which is just harder for the eye to distinguish from a "q". Getting rid of the stem on a "u" also makes it less distinguishable, and harder to read. And so on.
I'm genuinely confused as to how the philosophy for this typeface was developed, when it seems to go directly against basic established principles of legibility.
Re: JetBrains Mono: A free and open-source typeface for developers
#39I was disappointed that despite presenting the cookie banner as if it were a terminal, the options did not accept keyboard input [Y]es, I agree [N]o, thanks Ok on topic: I'm never sure what to think of these "developer" fonts that make use of ligatures for combinations like ==, >=, ->, =>, etc. On one hand they do look really nice, but I always can't help but feel it would actually make things just a little bit harde…
Regarding ligatures, I agree. I could live with the pointer arrow ligature, that's fine and looks nice, but not with the crossed '=' (that is "!=") or the symbol for >=. Call it ageing, but for the moment it stops my code reading flow. So "editor.fontLigatures": false
Re: JetBrains Mono: A free and open-source typeface for developers
#40This is a great-looking font, very well put together and a lot of thought put in to make it great for code. That being said, fonts are very personal. I compared it to PT Mono (Public Type, another open-source font) and have these observations: - Ligatures in JB are beautiful. I'm still undecided whether I like them in my code but the aesthetic value is pleasing. - Weight of JB Regular is heavier than PT. - Italics ar…
yeah this is what I noticed as well from samples and testing out on my code, same reason I'm not keen on Fira but prefer Consolas, letters are less regular and words have a different rhythm at a glance.