Earlier quoted context omitted.
I'm well aware. But that day will be when it stops working, and right now it still works fine. (Actually, it will be some time after that, since the day it stops working I will spend some time investigating how much work it would be to un-break it myself. The web can pry uMatrix from my cold, dead fingers. And I suspect I am not alone in feeling that way.)
Is there a reason to not use uBlock Origin? I’ll admit, I never used uMatrix, so I don’t know what it does; only adblockers.
Self-host your fonts for better performance
211–220 of 417 posts
Re: Self-host your fonts for better performance
#212Earlier quoted context omitted.
Well, good is relative. MacOS renders fonts in a weight-and-form-correct way which makes them look blurry however. Windows renders fonts in a weight-and-form-incorrect way, which however makes them sharper and easier to read on screens, especially with resolutions below 200dpi. Now if you use a high-resolution monitor and print-optimized fonts, MacOS will look better. If you use a low-resolution monitor and screen-op…
> Problem is, most designers come from print and use This can't still be true. No one comes from print anymore.
It is. The real problem is that a large number of designers like to have a pixel-perfect experience (which on print doesn't really matter as they know what paper will that publication use).
Re: Self-host your fonts for better performance
#213Earlier quoted context omitted.
I'm well aware. But that day will be when it stops working, and right now it still works fine. (Actually, it will be some time after that, since the day it stops working I will spend some time investigating how much work it would be to un-break it myself. The web can pry uMatrix from my cold, dead fingers. And I suspect I am not alone in feeling that way.)
Is there a reason to not use uBlock Origin? I’ll admit, I never used uMatrix, so I don’t know what it does; only adblockers.
Re: Self-host your fonts for better performance
#214Earlier quoted context omitted.
From TFA: > Since Chrome v86, released October 2020, cross-site resources like fonts can’t be shared on the same CDN anymore. This is due to the partitioned browser cache
Which is one of the many reasons I've stopped the almost hourly updates of Chrome. I feel fo people that have bad bandwidth or poor wireless connections. One of my favorite rants if web builders and more importantly the managers of team that build websites were forced to use a DSL speed level connection daily a lot of the cruft would go away.
Re: Self-host your fonts for better performance
#215I never understood why browsers don't ship with more fonts, especially Chrome.
Re: Self-host your fonts for better performance
#216Earlier quoted context omitted.
The cleaner look is because most designers use macOS which renders most fonts in a way that makes them all look good (let’s not get into technical details). On Windows the same fonts might look like shit (for example some parts of a character are thicker than the rest for no apparent reason)
MacOS makes text blurry. You need a high resolution monitor for macOS font rendering to be acceptable.
On hi-def monitors and laser-printed page, it is lovely both to read and to look at.
I mean, 4K (3840×2160) 23" displays nowadays start at $300, so if you’re still on hundred-buck 1920x1080 then you’re only getting what you paid for.
Going to all hi-def displays is the single best investment I ever made as a professional programmer, reading and writing text on screens daily.
Re: Self-host your fonts for better performance
#217This article isn't advocating saying goodbye to Google Fonts. It advocates not delivering them via CDN, but self-hosting them.
Yes it is...? Google Fonts is the service, not the fonts themselves. Check the "About" and "License" tab of any font on Google Fonts, they're not created by Google.
Re: Self-host your fonts for better performance
#218To the author, Google Fonts means "A CDN for fonts".
The article obviously talks about his definition, which may be confusing to people who use my definition.
Re: Self-host your fonts for better performance
#219Earlier quoted context omitted.
You’re underestimating how much work and skill it takes to make a good font, even for a great designer, so type foundries like to lock good fonts up behind rent-seeking license agreements.
Selling fonts is not rent-seeking. Rent-seeking would be if Google demanded money from a font designer to let their fonts be "compatible" with Chrome. I.e. Pay me or I'll make sure your product doesn't work with my product. App stores is a common example; pay Apple or they'll make sure your software doesn't run on the iPhone.
The most usual is that you'll have to pay a certain price up-front (or monthly), and some more for each access. The odds are also good that you won't be able to host the font yourself, because well, the foundry has to count those access, doesn't it? And if you want the foundry to respond any quickly, you better pay some extra.
Re: Self-host your fonts for better performance
#220As you can see, it is very sneaky by using CNAME Cloaking - https://i.imgur.com/VB2DB75.png
The request is to fonts.gstatic.com, but it resolves to gstaticadssl.l.google.com
Tracking using CNAME cloacking - https://medium.com/nextdns/cname-cloaking-the-dangerous-disg...