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?
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 :)
Repost, see https://news.ycombinator.com/item?id=45849342.
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.
Weird. I thought HN automatically combined submissions with the same URL unless there was like a year or so of space between them.
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 …
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?
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.
Might be nice if the ligature of != was ≠
Probably personal preference, but I prefer != not be smashed into one character.
as i mention in the description, Myna doesn't use ligatures. the Unicode sure looks very much like that in the font, though.
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"?!?!)
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 :)