Live data from Hacker News

FiraCode: Free monospaced font with programming ligatures

github.com

71–80 of 159 posts

Re: FiraCode: Free monospaced font with programming ligatures

#71
post #59
post #7

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/

I'm having trouble finding it now, but at one point I used a tool that put monospace fonts head to head (without revealing their name) and you would choose what you thought looked best. Jetbrains mono was my winner and I've been using it ever since.

I believe you're referring to this: https://news.ycombinator.com/item?id=29010443

Re: FiraCode: Free monospaced font with programming ligatures

#72

This is a stretch: > Your eye spends a non-zero amount of energy to scan, parse and join multiple characters into a single logical one. I don’t know how many calories are expended by the brain to perform this, but it has to be near-negligible. I am _extremely_ used to seeing characters as they are in ASCII, and retraining myself for some infinitesimal savings in visual processing seems like a net negative. Maybe this…

I'm pretty sure the eye spends exactly zero Joules on interpretation of visual stimuli. As for the brain, the brain doesn't see characters at the perceptual level, that it then needs to join at the cognitive level into tokens. At the perceptual level it just sees shapes. Whether it takes more energy to parse != or ≠ is something I don't anyone has ever researched.

You'd be wrong then, because it's (biomedical) textbook knowledge that quite a bit of processing of visual stimuli happens in the retina.

Re: FiraCode: Free monospaced font with programming ligatures

#74
post #28

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…

> It's a cute idea, but I found it more annoying to use in practice.

Agreed. Looks very nice in editor, but programming is not about looks. It's about ease of editing and maintainability.

Re: FiraCode: Free monospaced font with programming ligatures

#75
post #47
post #28

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…

I love it, wouldn’t want to program without it. The small quirks in editing are vastly outweighed by the improved readability of the code. Luckily we can each have our own way and still work on the same code.

"outweighed" or "vastly outweighed" ?

Re: FiraCode: Free monospaced font with programming ligatures

#77
post #61
post #28

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…

I agree. I respect that people use it, but it's really not for me. It makes the code harder to read IMO

Exactly. Personally I like to have it very obvious exactly what characters are in my file. But I also do agree that it looks very nice and can appreciate why people prefer it.

Re: FiraCode: Free monospaced font with programming ligatures

#78
post #69

Earlier quoted context omitted.

You might be surprised to hear that the eye actually does a lot of "preprocessing" for the brain.

Preprocessing is not the same as interpretation, in the same way that a pixel shader is not computer vision.

it does involve energy though, which was the original premis. Now whether total number of joules consumed over vs != vs ≠ is the real debate and gonna be hard to study I think...

Re: FiraCode: Free monospaced font with programming ligatures

#79

This is a stretch: > Your eye spends a non-zero amount of energy to scan, parse and join multiple characters into a single logical one. I don’t know how many calories are expended by the brain to perform this, but it has to be near-negligible. I am _extremely_ used to seeing characters as they are in ASCII, and retraining myself for some infinitesimal savings in visual processing seems like a net negative. Maybe this…

I'm pretty sure the eye spends exactly zero Joules on interpretation of visual stimuli. As for the brain, the brain doesn't see characters at the perceptual level, that it then needs to join at the cognitive level into tokens. At the perceptual level it just sees shapes. Whether it takes more energy to parse != or ≠ is something I don't anyone has ever researched.

A roughly fist-sized lump of your brain seems to be responsible for all the vision processing. It is as power-hungry as its size suggests.

Ever wonder why you can't really seem to read properly when you're hungry and tired? That part of your brain is in power-saving mode.

Re: FiraCode: Free monospaced font with programming ligatures

#80

This is a stretch: > Your eye spends a non-zero amount of energy to scan, parse and join multiple characters into a single logical one. I don’t know how many calories are expended by the brain to perform this, but it has to be near-negligible. I am _extremely_ used to seeing characters as they are in ASCII, and retraining myself for some infinitesimal savings in visual processing seems like a net negative. Maybe this…

Yeah, I read words all day and don't think my reading would be significantly improved if I started communicating in Chinese and read kanji. I'm sure one language is easier to read than the other but I doubt it is because their symbols are distinct per "word". I suspect that English readers don't read every individual character but rely a lot on word shape and I also suspect that people reading kanji do take some effort parsing particular features of the characters. I doubt there is a major fundamental difference.
Post reply on HN