Kelp
A UI library for people who love HTML, powered by modern CSS and Web Components.
It seems like the misguided perception of needing to use complex tools and frameworks to build a website comes from a thinking that web browsers are inherently limited. When, in fact, browsers have evolved to a tremendous degree
A UI library for people who love HTML, powered by modern CSS and Web Components.
Grrr…
Chrome, Edge and Firefox updates usually reach 95% of users within three months. But Safari updates are tied to a new release of the underlying operating system, so they take around 19 months to reach the same usage, and some updates may even need a new device.
This is so shameful. And glad as I am to see new features landing in Safari, as long as they hobble updates like this it’s all just pissing in the wind.
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.
This is clever: putting CSS inside a noscript
element to hide anything that requires JavaScript.
Everything you ever wanted to know about text-wrap: pretty
in CSS.
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 kind of ridiculous that this functionality doesn’t exist yet.
Here’s Clearleft’s approach to browser support. You can use it too (it’s CC-licensed).
Browser are user agents, not developer agents.