3 ms·

In my experience the default fonts on Apple devices are far and away the best fonts, period. They're better than almost every custom font, especially for reada

In my experience the default fonts on Apple devices are far and away the best fonts, period. They're better than almost every custom font, especially for readability.

kevincox 4y ago
I don't have an Apple device to test but does that mean that the author's point about the default `monospace` font "Courier New, is not legible" is out of date or just a rare opinion?
- KerrAvon 4y ago
  I think Courier is the only one of the fonts listed above that’s not sans-serif. The retro typewriter effect is not probably not what he wants for displaying a lot of prose in a modern context. I don’t think it’s actually illegible.
- qbasic_forever 4y ago
  Depends on your use, in the screenplay world Courier is mandated as the required font and anything not written in it is immediately trashed.
- myfonj 4y ago
  Probably very subjective. I, for one, am still using Courier New as my main monospace font, especially for code, and actually prefer having typewriter-y "serifs". No other serif-y monospace I've found fitted. I don't mind Consolas, and I like what is author using now (DejaVu Sans Mono), but their stance about varying reading experience depending on the OS makes me really, really devastated, because it just reflects a sad state of IT literacy and general adoption of basic philosophy of the web, which was built on premise that how content looks like depends both on author and user (through user agent) and fact that generic font family looks ugly is in other words defaults are bad combined with users have a bad taste and set bad default values. As was said, we are supposed to express our preferences in (through) our (user) agent's preferences. Most probably your browser will use four distinct fonts on this page, *all* of them (and more) you can define in your browser's or operating system's settings: data:text/html,<p lang="ja">iii<code>iii</code><p lang="en">iii<code>iii</code> It's sad that it is not a general knowledge.
  - myfonj 4y ago
    Fun fact: even though author have expressed a lot of opinions in their CSS, still for me the result is probably different from what they expected: since author does not define font colour, I see it in my default (not black but dark brown), plus paragraphs are slightly indented for me, since I limit their maximum width through userstyle. Funnily enough, background colour that author chose (and set, #F5F5F0) is nearly identical to my preferred background colour. Authors defining background colour without defining text colour is the reason we cannot effectively have default dark background and light text default in our UAs, because in this case we would see authors (light) background and ours (light) text.
pxc 4y ago
The Apple Color Emoji Font, the one you can't opt out of on Apple operating systems, is awful for readability. Pretty much inscrutable at small sizes.

In my experience the default fonts on Apple devices are far and away the best fonts, period. They're better than almost every custom font, especially for readability.

kevincox 4y ago

I don't have an Apple device to test but does that mean that the author's point about the default `monospace` font "Courier New, is not legible" is out of date or just a rare opinion?

KerrAvon 4y ago
I think Courier is the only one of the fonts listed above that’s not sans-serif. The retro typewriter effect is not probably not what he wants for displaying a lot of prose in a modern context. I don’t think it’s actually illegible.
qbasic_forever 4y ago
Depends on your use, in the screenplay world Courier is mandated as the required font and anything not written in it is immediately trashed.
myfonj 4y ago
Probably very subjective. I, for one, am still using Courier New as my main monospace font, especially for code, and actually prefer having typewriter-y "serifs". No other serif-y monospace I've found fitted. I don't mind Consolas, and I like what is author using now (DejaVu Sans Mono), but their stance about varying reading experience depending on the OS makes me really, really devastated, because it just reflects a sad state of IT literacy and general adoption of basic philosophy of the web, which was built on premise that how content looks like depends both on author and user (through user agent) and fact that generic font family looks ugly is in other words defaults are bad combined with users have a bad taste and set bad default values. As was said, we are supposed to express our preferences in (through) our (user) agent's preferences. Most probably your browser will use four distinct fonts on this page, *all* of them (and more) you can define in your browser's or operating system's settings: data:text/html,<p lang="ja">iii<code>iii</code><p lang="en">iii<code>iii</code> It's sad that it is not a general knowledge.
- myfonj 4y ago
  Fun fact: even though author have expressed a lot of opinions in their CSS, still for me the result is probably different from what they expected: since author does not define font colour, I see it in my default (not black but dark brown), plus paragraphs are slightly indented for me, since I limit their maximum width through userstyle. Funnily enough, background colour that author chose (and set, #F5F5F0) is nearly identical to my preferred background colour. Authors defining background colour without defining text colour is the reason we cannot effectively have default dark background and light text default in our UAs, because in this case we would see authors (light) background and ours (light) text.

pxc 4y ago

The Apple Color Emoji Font, the one you can't opt out of on Apple operating systems, is awful for readability. Pretty much inscrutable at small sizes.