Myna: monospace typeface designed for symbol-rich programming

52 pointsposted 3 months ago
by vinhnx

11 Comments

unwind

3 months ago

vinhnx

3 months ago

Strangely, I submitted this a week ago, even before the linked HN you mentioned. Now it turns to the front page, maybe the HN algo bumps it.

tyleo

3 months ago

Weird. I thought HN automatically combined submissions with the same URL unless there was like a year or so of space between them.

zygentoma

3 months ago

Why does the 'l' look different in the title image and in the example images?

I actually like the one in the title image more, because it's less likely to be confused for a 1.

[EDIT:] Also the kerning of l and i in 'lines' looks a bit off …

sayyadirfanali

3 months ago

designer here. thanks for the feedback. i've updated the serif in `l` after an issue raised the possibility of ambiguity with `1`. alas, that would mean i'd need to regenerate all the images, which i haven't done yet.

i didn't produce a variant for the `l` serif, please check issue #8. if you prefer the variant, please open an issue. can you elaborate on the kerning point, preferably there also?

amoss

3 months ago

The flat shape of the "r" and the lack of curvature on the "p" where it touches the stem would drive me mad, but YMMV.

ape4

3 months ago

Might be nice if the ligature of != was ≠

mrweasel

3 months ago

Probably personal preference, but I prefer != not be smashed into one character.

sayyadirfanali

3 months ago

as i mention in the description, Myna doesn't use ligatures. the Unicode sure looks very much like that in the font, though.

torstenvl

3 months ago

Font generally looks nice, but I really hate the trend of overly-curly curly braces.

(Also, I'm judging the C code. No check on the fopen()? fclose() on a possibly invalid FILE *? No return from int main()? "FILE *f"?!?!)

sayyadirfanali

3 months ago

thanks for the feedback. a few people have expressed the same criticism. i'm open to producing a variant with less-curly curly brances. please raise an issue, if you want to use it.

as is expected, all codes in the illustrations, especially the C code, are to be judged superficially, ie, by their covers, not content :)