A table showing how browsers prioritise a) the loading of JavaScript and b) the execution of JavaScript.
A history of front-end development that culminates here:
The frontier of 2026, the stuff the sharpest people are most excited about, is render the HTML on the server, ship almost no JavaScript, and use the web platform instead of fighting it.
This is an excellent one-stop shop of interface patterns:
This is an organic collection of common JS patterns that can be replaced with just HTML, CSS, and no, or very low, JS. As HTML and CSS continue to mature, this collection should expand.
This episode of the Shop Talk Show is the dictionary definition of “rambling” but I had a lot of fun rambling with Chris and Dave!
Progressive enhancement is about building something robust, that works everywhere, and then making it better where possible.
This is a spot-on analysis of how CSS-in-JS failed to deliver on any of its promises:
CSS-in-JS was born out of good intentions — modularity, predictability and componentization. But what we got was complexity disguised as progress.
Or, more precisely, why use React *in the browser*?
Web browsers provide you with great features for free. Why would you choose to use tools that stop you taking advantage of that?
Have you got the perfect talk for this event? Let me know!
A one-day event all about what you can in web browsers today: Brighton, March 12th, 2026. Tickets are just £225+VAT!
Some handy tips courtesy of Chris Ferdinandi.