No build frontend is so much more fun
The joy came flooding back to me! It turns out browser APIs are really good now.
Smart advice on future-proofing and backward-compatibility:
There isn’t a single, specific device, browser, and person we cater to when creating a web experience. Websites and web apps need to adapt to a near-infinite combination of these circumstances to be effective. This adaptability is a large part of what makes the web such a successful medium.
Consider doing the hard work to make it easy and never remove feature queries and @supports statements. This creates a robust approach that can gracefully adapt to the past, as well as the future.
The joy came flooding back to me! It turns out browser APIs are really good now.
Why single-page apps are just not worth it:
Here’s the problem: your team almost certainly doesn’t have what it takes to out-engineer the browser. The browser will continuously improve the experience of plain HTML, at no cost to you, using a rendering engine that is orders of magnitude more efficient than JavaScript.
Meanwhile, the browser marches on, improving the UX of every website that uses basic HTML semantics. For instance: browsers often don’t repaint full pages anymore.
Everything you ever wanted to know about text-wrap: pretty
in CSS.
This describes how I like to work too.
Some interesting experiments in web typography here.
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.
Safari 18 supports `content-visibility: auto` …but there’s a very niche little bug in the implementation.
It’s almost as though humans prefer to use post-hoc justifications rather than being rational actors.
Browser are user agents, not developer agents.
An alternate route to a declarative version of the Web Share API.