Sure thing. Thanks for following up. You can use the code TWENTYFIVE to get the course for $25. Cheers!

I think loading= lazy for video is a good one. I am currently poking around ideas for a patch to better speak to how it might work (should it block autoplay with the same heuristics? block poster from downloading? block metadata?) I think all three would be good. Planning to chime in on it this week

Hey there! Well, I decided to keep these coupons active until further notice in case you're interested. Use the code TWENTYFIVE to get access to the course for $25. Cheers!

Nodding as someone who published a browser extension to the chrome store that saved textarea values in Basecamp to local storage and offered them for retrieval

YUP

(Sorry to jump in. I didn’t make it to PerfNow this time but I really look forward to seeing Rich’s talk when it is released. Sounds like we’re on the same page in this thread 👍)

It’s for that reason that this particular pattern can have a massive impact on how soon pages are visible on budget devices and connection speeds. (Eg p90 and up). Presumably most have JS enabled, but when bundles are heavy, JS reliance is still causing their problem scottjehl.com/posts/this-c...

“JS-disabled” is often the first reason folks list for why to reduce JS reliance, but I’d rank it last (it’s real, but other reasons affect more people). The most common bottleneck I see in my work is delayed rendering and usability due to big JS bundles controlling HTML creation or visibility

why do I know @zachleat.com has dropped everything to start building already

I think delivering meaningful HTML from the server is table stakes for decent performance, so it's good! But the most popular "SSR" react stack struggles in core web vitals. It likely comes down to bundle size and DOM changes during "hydration." WCs are what I'd like to see too. Ecosystem needs help

Hey thanks, Robert! I hope you find it helpful

...and by standards-based, I mean patterns using *newer* standards now built into browsers. developed to make these libraries less necessary. The performance costs of snapping together UIs with heavy framework code are well known, but the demos and familiarity of just-use-React-again are very strong

also ianthehenry.com/posts/bauble...

really great stuff, @ianthehenry.bsky.social

hey Simon. A bunch, both online and in person at workshops as well throughout the past year. Happy to point to some links to testimonials on here if that helps. Thanks