Discussion
New post: "Do web components have a future if nobody is writing them?" https://nolanlawson.com/2026/10/19/do-web-components-have-a-future-if-nobody-is-writing-them/
Some thoughts on web components and AI coding. This was not an easy post for me to write.
@nolan I feel like the fact that this page fails to render anything useful on my web browser sums it up better than anything I could write myself. https://www.webcomponents.org/introduction
@nolan I find it's trivial to get agents to write Web Components. I literally just have "use vanilla JavaScript and Web Components" in my `CLAUDE.md` and that's it. There's excellent training material out there (thanks to people like you ❤️), so agents are really good at writing them. You have to know they exist, though, which is why pure vibe coders likely won't get them by default.
@tomayac Yep I've found this as well. I've also found that Claude chooses vanilla JS for sensible use cases (e.g. a lightweight app where a framework is overkill), so maybe it would choose web components for some use cases as well.
@nolan I’m a huge fan of web components as a way of getting separation of concerns between the data on a page versus the structure of its UI. Being able to do stuff like querySelectorAll to enumerate and filter the data on the page makes the browser dev tools console into a live editing environment/ REPL type thing
@nolan plus then you get the ability to have methods on your elements that allow them to talk to one another with well defined semantics, so components are durable intelligent things in the classic OO tradition
@revin That's a good point I hadn't considered – maybe for an agent it would be easier to use raw DOM APIs and element methods via something like the Chrome DevTools Protocol. Although I've found that my own agent tends to do this kind of thing with code updates and live-reloading rather than manipulating the page via the JS console.
@nolan agents can basically do anything equally easily no matter what the stack is, so for me it’s more about the semantics and composition and ad hoc inspection and so forth. Code that reads as basically directly what it *means* rather than mixing the mechanics in with the data management.
@nolan There’s a number of web components folks involved in MWG (myself included), so I don’t think it’s intentional that custom elements might be snubbed in the output. We could probably do a better job of mentioning good opportunities to use them as well as providing stronger guidance in favour of using them. Some of the newer guidance categories (e.g. `guides/ui-components`) are a good fit for doing just that. (Opinion: completely my own)
In case you don’t know, the fuller source for the project is here: https://github.com/GoogleChrome/modern-web-guidance-src
@knowler Ah, I didn't know that – thanks for the tip! I assumed it was some kind of internal Google project being synced with an OSS repo.
I'm glad to know that web components folks are involved in MWG! BTW I'm not necessarily arguing that it needs to push for WCs harder; I actually thought its text was pretty even-handed (matching some of my own pro- and anti- positions in the post). I'm still concerned about how WCs will fare in the broader vibecoding context though.
Install Fedizen
Get the full app experience
@nolan personally I think both agentic AI *and* web components are a blight on the software industry. I also have a lot of grumpy curmudgeon opinions about React.