Live data from Hacker News

B612 Font Family

b612-font.com

81–90 of 99 posts

Re: B612 Font Family

#81
post #24

Another font that has a similar aim is https://en.wikipedia.org/wiki/Atkinson_Hyperlegible I find that it strikes a balance between aesthetics and legibility. Two differences I noticed immediately are the 0 and I characters which are much more difficult to distinguish with this font.

This looks much better than B612. B612 just looks... awkward. It has these weird little cut-out areas at the intersections of some of the lines. I don't get it. Makes it looks like it's awkwardly pasted together from disparate pieces.

Re: B612 Font Family

#82
post #60
post #59

Earlier quoted context omitted.

That font does look really nice! Also noticed the slash in the 0 runs top left to bottom right, rather than the far-more-common [in my experience] top right to bottom left Any idea why that decision was made?

An obvious explanation would be that this helps distinguish it from øØ (as in Danish and Norwegian), which is slashed from bottom left to top right. The Wikipedia article does demonstrate its legibility when blurred.

> which is slashed from bottom left to top right

interesting way to describe this in that it is described in reverse order of how i've always seen it. my first thought is that's because it is also opposite of how i would draw it when writing by hand.

Re: B612 Font Family

#83
post #50
post #24

Another font that has a similar aim is https://en.wikipedia.org/wiki/Atkinson_Hyperlegible I find that it strikes a balance between aesthetics and legibility. Two differences I noticed immediately are the 0 and I characters which are much more difficult to distinguish with this font.

Huge endorsement for Atkinson Hyperlegible from me. As someone with horrible and declining eyesight in multiple ways, it has improved my computing experience a lot. There’s been a couple of attempts at making a monospace version, I currently use the one by Edward Shin in my editors and terminal https://github.com/Hylian/atkinson-monolegible

thanks for sharing this monospace version, i've been using atkinson as my browser's sans-serif font

Re: B612 Font Family

#84

Strange, the background image of the site's header shows a very nice cockpit font indeed, but the actual B612 font is quite different - for instance zeros have no line through them. Though the oxygen indicator seems to use this font.

It's really unfortunate that this glaring issue stops wide adoption. The slash through the zero should have been the default, very silly for the official release to omit that.

Re: B612 Font Family

#85
post #24

Another font that has a similar aim is https://en.wikipedia.org/wiki/Atkinson_Hyperlegible I find that it strikes a balance between aesthetics and legibility. Two differences I noticed immediately are the 0 and I characters which are much more difficult to distinguish with this font.

"Atkinson Hyperlegible is a freely available typeface built around a grotesque sans-serif core,..."

So obviously my understanding of the definition of grotesque is not what's meant as its use in relation to fonts, but the definition in a font's use is just odd on why it is used in this manner.

https://en.wikipedia.org/wiki/Grotesque_(Stephenson_Blake_ty...

Re: B612 Font Family

#86

Welp, it's a failure because the capital "i" does not have crossbars... making it indistinguishable from a lower-case L. Such a tiresome defect in one font after another.

I wouldn't say it's indistinguishable - the lower case L has a curved bottom.

But you don't know that unless they're both being displayed at the same time.

Re: B612 Font Family

#87
post #29

Seems really bad to me. There's a lot of distracting glitches like the K and Q having small gaps where strokes come together, and even glyphs like the N, M, Y and Z have weird little gaps at the joints, the F and B have a bizarre overhang at the upper horizontal stroke, the 1 and 6 have a weird cut in their strokes. There are lots of weird confusing choices like the parenthesis being a round rect instead of a bow sha…

I think these “ink traps” might be effective on low resolution displays. But yes, those parentheses indicate it’s not a coding font.

Yeah, there's a visual example here of how it helps the 'e' stay legible at low res:

https://intactile.com/projets/ameliorer-la-lisibilite-et-la-...

Without that "pixel trap" (?) the intersection (there's probably a fancy typographic term for this) would look too bulky.

Re: B612 Font Family

#88

It's very interesting that I picked this font for my live coding language: https://quaverseries.web.app/ The main reason is that I need to use a syntax to represent a music sequencer such as ___65. B612 can separate two or more underscores perfectly. For a long time, it's always my first choice of coding font although I have no idea on its origin. I just feel it looks great when I browse all Google fonts. But it's gr…

it does look great on ur site!

Thanks! I realised later that it has an issue with parenthesis (). So I had to switch to Fira Code for https://glicol.org/

Re: B612 Font Family

#89
post #81
post #24

Another font that has a similar aim is https://en.wikipedia.org/wiki/Atkinson_Hyperlegible I find that it strikes a balance between aesthetics and legibility. Two differences I noticed immediately are the 0 and I characters which are much more difficult to distinguish with this font.

This looks much better than B612. B612 just looks... awkward. It has these weird little cut-out areas at the intersections of some of the lines. I don't get it. Makes it looks like it's awkwardly pasted together from disparate pieces.

Those cut-outs look a bit like ink traps, though whether that actually makes any sense in a font unlikely to be used with actual ink, I do not know...

Re: B612 Font Family

#90
post #60

Earlier quoted context omitted.

An obvious explanation would be that this helps distinguish it from øØ (as in Danish and Norwegian), which is slashed from bottom left to top right. The Wikipedia article does demonstrate its legibility when blurred.

> which is slashed from bottom left to top right interesting way to describe this in that it is described in reverse order of how i've always seen it. my first thought is that's because it is also opposite of how i would draw it when writing by hand.

yeah ... I thought about "top right to bottom left"

because then you are comparing top to top

instead, i kept it left to left :)

Post reply on HN