31–34 of 34 posts
I was going to say that font is unreadable, but its Courier New. By my own extensive testing[1], it's optimal at minimum 18px, you're at 13.5px. [1]: https://github.com/Diablo-D3/dotfiles/blob/master/fontsizes....
edit: I just noticed a newer comment from OP saying that changed the font size.
Earlier quoted context omitted.
Courier New is a bad font that no one should choose to use. In typical font-weight terms, where Regular should be 400, it’s 200–250, because it was improperly digitised, not taking ink bleed into account. Windows put some hacks into ClearType to make it render a little less badly, but they’re not dependable these days. (“Courier”, as provided by macOS, is fine. But Courier New is irredeemably bad.) Concerning font-fa…
It renders terribly on sizes below ~14px, even on a Retina display. No anti-aliasing setting can save it. A modern typeface like IBM Plex Mono [1] or Office Code Pro [2] that offers more weights and can still render nicely at 10px size would be a better choice, maintaining the same aesthetic. [1] https://fonts.google.com/specimen/IBM+Plex+Mono [2] https://open-foundry.com/fonts/office-code-pro
Earlier quoted context omitted.
Zero code is in your head if you can't read it. The predominant monitor in existence is your average 24" 1080p monitor, sat at, on average, 32" away from the head. The average person has worse than 20/20 vision. You must test your website in such conditions and make sure it is readable, and also make sure it meets at minimum WCAG A, but preferably the whole way to AAA if possible.
Thank you but the predominant monitor's probably a smartphone. The average professional is probably using a 4k monitor at the moment. Everything in the free documentation I've provided you out of my own time and money that you're referring to exists in relation to the other elements in that page, so to get the experience you're after simply ctrl+scroll and change the CSS zoom level like the riot at parties that you c…
Earlier quoted context omitted.
Would you prefer to see ESM or neither?
ES6 modules. Tooling can take care of generating UMD from that as a single source of truth and since it’s the language standard for years now it’s the best supported format in the ecosystem. At this point UMD/CommonJS/etc are historical artifacts only useful to legacy codebases and by now they’ve all adopted whatever ESM->legacy compilation pipeline they need.