JetBrains Mono: A free and open-source typeface for developers
121–130 of 207 posts
Re: JetBrains Mono: A free and open-source typeface for developers
#122Re: JetBrains Mono: A free and open-source typeface for developers
#123We should take a lesson from the FAQ about license. It is the simplest yet most useful one I have seen! -- May I install JetBrains Mono on my system and use it in any code editor? -> YES. May I make and print a poster with JetBrains Mono? -> YES. May I use JetBrains Mono in my logotype? -> YES. May I use JetBrains Mono on my website? -> YES. May I use JetBrains Mono in my applications? -> YES. May I design my own fon…
IANAL - I am pretty certain you can do most of those things with all fonts regardless of license. Copyrights on fonts is almost non-existent. The only thing copyrightable is the actual "code" used in the font. (maybe delivering their files on a website is an issue?) This is based on research I did years ago when dealing with a copyright legal case where I worked. The summation is that you can't copyright the alphabet…
But If I take a font file someone else made, not one I created myself to look like it, then its a whole other story. The font industry is cutthroat and quite lawyer happy, too (which is why tracing them to make your own is so popular...and brutally expensive if you hire a contractor to do it for you). You still usually come up ahead if you're a big company though by making your own.
Re: JetBrains Mono: A free and open-source typeface for developers
#124Great 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).
Re: JetBrains Mono: A free and open-source typeface for developers
#125I 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…
I misread 'a's as 'o's in the example provided. Probably result of all three points combined...
Is that common in fonts and I never noticed before?
Re: JetBrains Mono: A free and open-source typeface for developers
#126Can I control which weight is used in JetBrains IDEs for "bold" text? It looks to be using the bold font weight, when I'd prefer to use medium.
For multi-weight font they shows up as different font in the list. Fire Code light, Fire Code medium, ...
For example: Settings > Editor > Code Style > Style Sheets > CSS <-- no way to control the font weight used for bold-rendered property values
Re: JetBrains Mono: A free and open-source typeface for developers
#127I 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…
Re: JetBrains Mono: A free and open-source typeface for developers
#128I will say, I do like a few of the changes, but not sure if I'll be switching from Inconsolata/Consolas any time soon.
Re: JetBrains Mono: A free and open-source typeface for developers
#129I like it, this might finally be the font that gets me to drop Fira Code. It's missing Powerline symbols, though, which is a strange omission for a developer font in 2020.
This. Makes it hard for me to use it for VIM as my terminal needs Powerline. It's otherwise a very nice font.
Re: JetBrains Mono: A free and open-source typeface for developers
#130I 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…
With a good deal of skepticism, I switched the environment where I do about half of my work to a font with ligatures some time ago. Just to try it out for a while. I happily forgot that I had done it as a trial, and upon reading this headline caught myself hoping that there would be ligatures. I actually find that it provides an almost haptic feedback when going between things like =, == and ===, and I think I miss i…
Aside: Hopefully this font has box and line art characters and they align properly... this is a huge short coming in a number of fixed-width fonts that should be rectified.