51–60 of 159 posts
Ligatures, IMO, make for a bad coding editor experience. No, I do not want >> parsed as a right shift when it's actually used as two adjacent template delimiters. And no, I'm not okay with the inconsistency that results from the usage of different operators from one programming language to another. Want to change a != to a == operator? Enjoy futzing with placing the cursor properly. It's a cute idea, but I found it m…
Ligatures, IMO, make for a bad coding editor experience. No, I do not want >> parsed as a right shift when it's actually used as two adjacent template delimiters. And no, I'm not okay with the inconsistency that results from the usage of different operators from one programming language to another. Want to change a != to a == operator? Enjoy futzing with placing the cursor properly. It's a cute idea, but I found it m…
You can always use the original version without ligatures, Fira Mono, available here: https://fonts.google.com/specimen/Fira+Mono
Ligatures, IMO, make for a bad coding editor experience. No, I do not want >> parsed as a right shift when it's actually used as two adjacent template delimiters. And no, I'm not okay with the inconsistency that results from the usage of different operators from one programming language to another. Want to change a != to a == operator? Enjoy futzing with placing the cursor properly. It's a cute idea, but I found it m…
> No, I do not want >> parsed as a right shift when it's actually used as two adjacent template delimiters. I don't like ligatures either, but I think that this depends on the editor. For example, if typing Rust in IntelliJ, if you type `Box >`, it will show two regular ">" characters. But if you type `x >= 3`, it will replace it with a single glyph. https://ibb.co/Dzx0LFG
I've tried ligatures in coding for a few months but eventually decided against them. The small parsing overhead isn't worth it just for beauty. The philosophy of form follows function wins again.
I think it’s because operators like != are actually considered a singular symbol not two characters. We just don’t have that many available keys so we use multiple characters. But in my mind it’s a single symbol and ligatures go a long way to help my brain parse it that way
Ligatures, IMO, make for a bad coding editor experience. No, I do not want >> parsed as a right shift when it's actually used as two adjacent template delimiters. And no, I'm not okay with the inconsistency that results from the usage of different operators from one programming language to another. Want to change a != to a == operator? Enjoy futzing with placing the cursor properly. It's a cute idea, but I found it m…
Of course, this is all very subjective, but I do find Fira Code to be a beautiful coding font. I also appreciate having ligatures in fonts nowadays. Fira Code was my go-to for a long time, but I've come to increasingly use Jetbrains Mono which is available under the same Open Font Licence and is quite similar (although slightly preferable visually to me). https://www.jetbrains.com/lp/mono/
Hi! I’ve returned once more to recommend the Input family of typefaces. https://input.djr.com/ I’ve been code using Input Sans a (gasp!) proportional coding font for years now and I love it. Input also comes in a monospaced version FWIW.