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 :)
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 …
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?
(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"?!?!)
as is expected, all codes in the illustrations, especially the C code, are to be judged superficially, ie, by their covers, not content :)