This is a really excellent four-part series on web performance that really dives into the technical details and asks all the right questions:
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.
Grrr… it turns out that browsers exhibit some very frustrating behaviour when it comes to the video element. Rob has the details…
I have to agree with John here:
There’s absolutely no reason the mobile web experience shouldn’t be fast, reliable, well-designed, and keep you logged in. If one of the two should suck, it should be the app that sucks and the website that works well. You shouldn’t be expected to carry around a bundle of software from your utility company in your pocket. But it’s the other way around.
There’s absolutely no technical reason why it should be this way around. This is a cultural problem with “modern front-end web development”.
Here’s a handy free tool from Calibre that’ll give your website a performance assessment.
This is grim:
If you look at the data below on how popular websites today are actually transpiling and deploying their code to production, it turns out that most sites on the internet ship code that is transpiled to ES5, yet still doesn’t work in IE 11—meaning the transpiler and polyfill bloat is being downloaded by 100% of their users, but benefiting none of them.
In which I find a tagline for Web Day Out and a tagline for React.
Making a checklist of things that fall somewhere between front-end and back-end development.
Technically, websites can do just about anything that native apps can do. And yet the actual experience of using the web on mobile is worse than ever.
A redesign with modern CSS.
Safari 18 supports `content-visibility: auto` …but there’s a very niche little bug in the implementation.