21–30 of 89 posts
Not related to this awesome font, but is it just me who doesn't like fonts ligatures? I'd much rather see !=, than crossed =.
Thank you for 1) making the font I’m actually going to try using it in VSCode simply because I think it will be fun and oddly enough easy to read, and 2) teaching me what a ligature is.
Not related to this awesome font, but is it just me who doesn't like fonts ligatures? I'd much rather see !=, than crossed =.
Ligatures are amazing, I don't understand why anyone would like ascii "compound versions" of a set of symbols when there are thousands if not many hundreds of thousands of great symbols that were used in older typographic settings that are available for usage.
- It makes me have to think too hard to figure out where the boundaries actually lie between characters when I want to edit. I don't want to think about how many times I'll have to press backspace to delete a single "character"; without ligatures, I don't have to think at all. - With ligatures enabled, I have to remember how to type each character-group (e.g., that != is the same as slashed equals). With ligatures disabled, I can just read it back from an existing example. In other words, ligatures create a separation between what I type and what I see. - It makes it hard to quickly compare my code to examples online that don't use the ligatures because, again, I'm forced to translate between what's on my screen and what's in the file.
The only ligatures I appreciate are minor stylistic ones, e.g., raising a colon slightly before a number, adjusting the spacing between two consecutive colons, raising two consecutive asterisks, etc. Changes that don't fundamentally change the code appears but make it a teensy bit more aesthetically pleasing.
It's cute! Some people will enjoy it, may be brighten their day during some nasty debugging. I wonder how it does for people with dyslexia. I'm guessing not great.
On the topic, I recently learned about the Dyslexie font [0] as well as OpenDyslexic [1]. You can see the goal is to make characters easily differentiated. Not sure how I feel about these fonts—I can certainly read them easily, but I am not a fan of the style. There are other fonts I can read just as well which look better too.
cool. too many single-pixel gaps to be usable. the diff btw c and o shoudln't be a single pixel
2) it's meant to be rendered large enough that this doesn't matter
3) "bitmap" fonts always have compromises to fit the limitations of the grid
It's cute! Some people will enjoy it, may be brighten their day during some nasty debugging. I wonder how it does for people with dyslexia. I'm guessing not great.
I have dyslexia and I can tell I have to slow down a bit when reading this, but it’s not bad. I assume the closeness between characters makes it slightly worse for everyone, especially with characters like “o” and “c” differing by a single pixel. On the topic, I recently learned about the Dyslexie font [0] as well as OpenDyslexic [1]. You can see the goal is to make characters easily differentiated. Not sure how I fe…
Not related to this awesome font, but is it just me who doesn't like fonts ligatures? I'd much rather see !=, than crossed =.
Ligatures are amazing, I don't understand why anyone would like ascii "compound versions" of a set of symbols when there are thousands if not many hundreds of thousands of great symbols that were used in older typographic settings that are available for usage.
Curious how font ownership works, especially with pixel fonts. If I make my own font from scratch, and it matches per-pixel an already-created font, is it mine or theirs?
This seems like a fairly comprehensive answer: http://www.faqs.org/faqs/fonts-faq/part2/ "First, the short answer in the USA: Typefaces are not copyrightable; bitmapped fonts are not copyrightable, but scalable fonts are copyrightable. Authorities for these conclusions follow."
I actually find it odd that "typefaces" are not copyrightable, but I think that's more of an historical quirk than some wise feature of the legal system.