How progressive image rendering works in browsers today, and how it could work in future. There's a bunch of stuff here that's contrary to popular belief, like "AVIF can't render progressively" (it can) and "JPEG XL does" (it doesn't in Safari). jakearchibald.com/2025/present-a…

Signals flip the script. React renders where you create state. Signals render where you use state. Same state, but you are pushed into patterns that will lead to better performance by default. One paradigm shift away from memoization hell. 🎯 jovidecroock.com/blog/state-vs-…

New in Firefox nightly (146.0a1 2025-10-19): large lists of unused CSS custom properties are collapsed by default. This not only reduces clutter, it also massively speeds up the rendering of the inspector panel in some cases.

A lot of people didn't realise this post contains a link to an article. X's UI is so (intentionally?) bad at this.

Last week I posted about a secret config in Firefox that made view transitions easier to debug. SP said we should make it less secret. So we did.

I tried to AI code some in-browser video decoding stuff. It made a mess. So I learned the APIs somewhat properly, and did a much better job, but it was still messy. Then I found mediabunny.dev and it just worked. Yay!