The History of Web Performance | Scott Jehl, Web Designer/Developer
There are two eras.
(scottjehl.com)
There are two eras.
(scottjehl.com)
Happy Friday! Know anyone looking to start learning about Web Components this weekend? Let 'em know there's a 10% off promo running on my online course until Monday. Just use the code TENTENTEN at sign-up. https://scottjehl.com/learn/webcomponentsdemystified/
@zachleat short for ex-large
@pixelambacht @zachleat @svgeesus @niutech @konnorrogers I dropped a comment at the end to try and figure out where this is at. I'll plan to blog any findings that are useful https://github.com/google/fonts/issues/1067#issuecomment-2321425373
@pixelambacht @zachleat @svgeesus @niutech @konnorrogers Thanks @zachleat. Still, I'm inclined to wonder that if there were a reliable way to use font-face and point to one url, if that'd still be quite a bit faster than the current default render-blocking 3rd party round trip for font-face rules that reference a slightly better file for some browsers.
here's that thread where G says not to rely on the URLs, fwiw https://github.com/google/fonts/issues/1067#issuecomment-438848947
@pixelambacht @svgeesus @niutech @konnorrogers Yeah. I'd like to know more about whether or not one of the woff2 formats works across devices, and the cost if it means including the hinting.
@svgeesus @niutech @konnorrogers Yeah, maybe. I'd love to see a reliable workaround. The issue, as I've known it for a while at least, is that the font file urls aren't stable for long.
@niutech @konnorrogers I'll write it up soon but the issue is the font file hashes periodically change and aren't reliable. That's just the google fonts situation, among others
Sure, self-hosting fonts is ideal, but I suspect the most important part is our ability to self-host the CSS font-face rules that reference the fonts, wherever they are.
CSS/Fonts: It's really unfortunate that the typical patterns for loading web fonts from providers (Google Fonts, etc) start with a render-blocking third-party request just to get the @font-face CSS rules (note: not the actual fonts yet) which should ideally be in our own CSS from the start. I should blog about the reasons we can't do that reliably with many providers, but it's such a shame we can't because leading with a performance anti-pattern transfers the cost of the service to the users.
Announcement! My online course, Web Components Demystified has been released! Learn to build dynamic, fast, accessible, and resilient web apps with standard web components today. 8+ hours of training. Team discounts available! https://scottjehl.com/learn/webcomponentsdemystified/
@zachleat I'm sure there's a good answer to this but is there a reason SVG isn't supported by opengraph? Seems like it'd be a nice way to point to a composed graphic and avoid these screenshot services (however genuinely cool they are)
@zachleat Yes. I recall using a similar metaphor around 2013 about the electricity in a home being the JS and that the "shelter" part of the home should work well regardless of whether the power is on and people actually got pretty upset, but that was back when folks were writing posts saying progressive enhancement is dead.