An extremely cool ping/pong of ideas teasing out what good browsers can do with almost no code in these posts:
I spent hours and hours trawling through the sites of some of the world's best web developers, and despite the horrors I regularly experience in my daily work in Big JavaScript Territory, what I saw left me hopeful:
Just published a new section on my site to capture references to a lot of the essential web performance and fundamentals-oriented webdev resources I find myself continually directing folks to. Also, lots and lots of links to blogs I love:
The dirty JS hacker in me loves this (ab)use of `PerformanceObserver` so much:
I've been pretty lax about keeping up with the webperf slack, but this was in the scrollback from March, and I love that it shows so directly how understanding the rendering engine unlocks better experiences for everyone, not just folks on low-spec machines and networks:
Every engineer worthy of the title adopts one unshakeable article of faith: POPULARITY IS NOT A QUALITY METRIC
Things I would like every young web engineer to learn: - anything you can do in CSS + HTML, you *should* do in CSS - *framework du jour* is not a platform, it's a high-interest loan against your future capacity. The platform is the platform - understanding the memory hierarchy *always* matters - client-side isn't easier than the server, and "generalists" usually suck at client-side. Mind the (packet) gap - managers who are not technical are not useful - put users first, always
Safari at WWDC '25: The Ghost of Christmas Past
React: cheap, fast, good; choose none.
Lots of folks fell for the "DOM is slow" marketing of certain frameworks, but DOM isn't slow. *Uncontrolled style read-back* is. But what if that wasn't a thing? Looking for feedback on a new proposal to control layout thrashing here: πŸ“ƒ.md