131–140 of 154 posts
A typeface designed for programming should have _very_ visually distinct bracket and parentheses {([])} characters. Intel’s new typeface and the GitHub family that was just released both do this very well. I’d advise the Victor Mono author to take a look at how those fonts do it.
Earlier quoted context omitted.
It's a shame this is all you got from the response because I think what they said is actually a lot more interesting: > Thanks for trying the font and having lots of thoughts. You're right that it doesn't follow all of the guidelines to maximize readability! There are other fonts that do that but mine does not. That's not what I'm interested in and it doesn't bother me - I find it to be perfectly readable. I think an…
>I think what they said is actually a lot more interesting Your rewriting of the comment says exactly the same thing it did before. My assessment of it remains the same. I think an important part of maturing as a developer (and a human) is realizing that it's better to say nothing at all than to write "it works for me, use something else if you don't like it" in response to criticism of work that you: 1. Publish onli…
Big fan of Iosevka Term Regular for programming. The condensed font takes a day or two to get used to, but it gives you a lot of extra screen space. https://typeof.net/Iosevka/
Iosevka is such a nice font, ever-evolving, and surely what I would have used if I hadn’t enjoyed Victor Mono more :)
Earlier quoted context omitted.
Typeface designer here. Thanks for trying the font and having lots of thoughts about it. I guess the point is that it wasn’t first and foremost designed to follow as many font design principles as possible. If that’s what’s important to you, pick a font that follows as many of these principles as possible. :D In the end, I guess I don’t really care whether I use 157ms to parse a sentence instead of 158 - although to…
Hey, thanks for designing it. Right now I'm using Iosevka but I loved Victor Mono, was my main terminal typeface for a long time, and I loved the high x-height which enhanced readability even at low sizes. Even today it's one of my recommendations for anyone looking for a coding/monospace font.
I'm generally pretty supportive of new typefaces, but this one strikes me as... not very legible. The x-height is so uncommonly high it makes it genuinely difficult to distinguish between uppercase/ascending and lowercase letters at a glance (e.g. 'U' vs 'u', or 'h' vs. 'n'), and similarly the descender is so tiny it makes it hard to distinguish certain letters at a glance (e.g. 'q' vs 'p'). The whole point of large-…
Same reaction here. Legibility is below-average, and I don't love the look & feel either.
I'm generally pretty supportive of new typefaces, but this one strikes me as... not very legible. The x-height is so uncommonly high it makes it genuinely difficult to distinguish between uppercase/ascending and lowercase letters at a glance (e.g. 'U' vs 'u', or 'h' vs. 'n'), and similarly the descender is so tiny it makes it hard to distinguish certain letters at a glance (e.g. 'q' vs 'p'). The whole point of large-…
This is exactly my thought. I can't tell what's uppercase or lowercase without really analyzing each word.
I wish we could get a new HN guideline to not make comments for or against ligatures in monospaced fonts. You're not going to convince anyone.
Sorry, ligatures are not for me. I don't get it. Why would you ever want symbols to collapse like that in a functional monospace font? Just looks like a bunch of funky unicode characters peppered throughout my source. And my caret can travel _inside_ one of these special marks? No thanks.
Of course plenty of people far more experienced than me use them; they still look like clowns though.
All these new typefaces ... I think it is time for a new keyboard design to make use of those cool Unicode codepages. I see so many symbols that would be great to have in new programming languages but somehow we're stuck with ASCII and I think keyboards are the culprit.
I generally do quite fine with my Compose Key configuration, though (even on Windows, where I use WinCompose). [3]
[1]: https://docs.julialang.org/en/v1/manual/unicode-input/