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…
My font didn't change (Still Fira Code), but the look of the text changed in last update. Hard to put my finger on. Some of the text looks more blurry, and I'm noticing more bold than before, but I can't tell if that's mismemory or not.
JetBrains Mono: A free and open-source typeface for developers
141–150 of 207 posts
Re: JetBrains Mono: A free and open-source typeface for developers
#142I 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…
The first thing I checked for here was ligatures; this font would not have gotten five seconds of my time otherwise.
If one doesn't want ligatures, one turns them off. No one should design a programming font in 2020 without ligatures, just like no one should design a programming language in 2020 without a language server to handle editor services.
In a language like Haskell with many compound operators, the code just looks stupid and irritating without ligatures.
I may be at one extreme here, for I absolutely loathe comment characters. I've programmed preprocessors for each language that I use, with defaults that flush left is a comment (to be appropriately syntax colored, and with a convention for blocks that include indentation) and indented is code.
Re: JetBrains Mono: A free and open-source typeface for developers
#143I always applaud efforts at new typefaces, but unfortunately I feel this is a badly designed typeface that is worse for legibility, not better. Addressing their three main points in turn: > 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 up…
Over the last 10-15 years or so, I’ve tried so many of these new fonts but always just end up back to DejaVu Sans Mono Bold. Now that my eyes are getting older, it works even better. On a Mac, Menlo looks nearly identical.
Re: JetBrains Mono: A free and open-source typeface for developers
#144To me, everything is too thick and crammed together compared to Fira. It just feels like the font wasn't designed with enough letter spacing. I think you can manually control this in IntelliJ products, but the default spacing seems too crammed.
Re: JetBrains Mono: A free and open-source typeface for developers
#145Re: JetBrains Mono: A free and open-source typeface for developers
#146Earlier quoted context omitted.
A lot of the details they spent so much effort on didn't make any sense to me as to why that particular design detail would be important. I don't care about vertical alignment of letter shape details. If I need lowercase letters to look bigger, I almost always also need uppercase bigger too, so I'll just increase the font size +1 pt. I use three different fonts in terminals, editors and IDEs. So I'm sure this font wi…
> A lot of the details they spent so much effort on didn't make any sense to me as to why that particular design detail would be important. IMHO, fonts have been studied too deeply for too long for some graphic designer at J. Random Corporation to be able to easily make improvements. In situations like that, most changes and new ideas end up being regressions.
Re: JetBrains Mono: A free and open-source typeface for developers
#147Earlier quoted context omitted.
I misread 'a's as 'o's in the example provided. Probably result of all three points combined...
I'm super confused, are the using a... well, I don't know the terms, but a fancy "a" for the straight face and a simple "a" that's the circle-bar O|-shaped "a" for italics? Is that common in fonts and I never noticed before?
Re: JetBrains Mono: A free and open-source typeface for developers
#148Great to see that they’ve attributed Nikita Prokopov, the creator of FiraCode. While not the first, he expanded the ligatures in Hack, and Hasklig fonts and Jetbrains eventually bundled Firacode in their products. Quite a nice course of open source development over the years (I have been following the updates since ~2016).
You know that @tonsky works for them now, right?
Re: JetBrains Mono: A free and open-source typeface for developers
#149Earlier quoted context omitted.
This is why I love how configurable editors are now days. I absolutely adore ligatures in my programming fonts. I've been using FiraCode for at least a year or 2 now, and while i'll be the first to admit that the reason I enabled ligatures was because they looked cool, now I really miss them when they aren't there.
I'd much rather see languages take advantage of characters outside of ASCII. There are already symbols such as ⇒ which could be used by a language. This is a nice feature of APL, and the derivatives such as J which use plain ASCII are much less nice to work with.
Re: JetBrains Mono: A free and open-source typeface for developers
#150Thanks, 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…
My font didn't change (Still Fira Code), but the look of the text changed in last update. Hard to put my finger on. Some of the text looks more blurry, and I'm noticing more bold than before, but I can't tell if that's mismemory or not.