2026-06-23
Hey friends,
I try not to tell dad jokes.
But when I do, he thinks they’re really funny.
(Happy Father's Day to all the dads out there!)
Web Components are weird.
I REALLY want them to be a thing. I love the promise of 'it works everywhere!'... but in almost every instance that I've worked with them, they've been a pain.
Dave Rupert had some thoughts a few years ago on why they haven't taken over the internet. These all add up to a certain friction when trying to implement them. They're slow, arcane, and can be implemented poorly, leading in some cases to mountains of JavaScript that start to make you question why you're using them at all.
But it's not all bad. Nolan Lawson reminds us they're exceedingly good for client-rendered leaf components, for agnostic-all-the-things drop-ins. People often cite design systems as a good use case as well, which I agree with in theory. I would argue that they are the harder path for a design system, only useful if you TRULY need the encapsulation and portability.
I like this quote that Nolan surfaces from Ryan Carniato:
"[I]n a sense, there is nothing wrong with Web Components as they are only able to be what they are. It’s the promise that they are something that they aren’t, which is so dangerous."
They're not a framework replacement. They have their problems, but they have strengths too.
I'm still rooting for web components.
Web Stuff
Other Stuff
👽 Weird, 📺 Watch, and 🎮 Play
Don't miss what's next. Subscribe to Net Noodlings with Nathan: