Modern browsers now support everything needed to build sophisticated, reactive web interfaces without React, Vue, or Angular. Web components, custom elements, shadow DOM, and native event systems l...

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

Modern browsers now natively support everything needed to build sophisticated, reactive UIs without React, Vue, or Angular. Web components — built on Custom Elements, Shadow DOM, templates, and the native event system — offer encapsulation, loose coupling, and long-term stability that frameworks cannot match. The article argues that the browser has effectively become the framework, and that the upgrade treadmill, dependency overhead, and abstraction layers of popular frameworks are avoidable. It walks through practical patterns: event-driven component communication using custom events that bubble up the DOM, data flowing down via attributes and properties, and Shadow DOM for true style encapsulation. A dashboard example illustrates how independent panels can respond to shared filters without global state or prop drilling. The piece acknowledges frameworks still make sense for teams with deep existing expertise, but advocates for web components — especially for new projects, smaller teams, or long-lived products — and suggests AI assistants can accelerate the learning curve.

Web Components: The Framework-Free Renaissance

Building Modern UIs Without the Framework Tax

Shadow DOM: Encapsulation That Actually Works

Solid article and I agree web components are underused, but I think it undersells what frameworks actually give you.
I’ve been building with Vue 3 and React for years. The component model (props, slots, events) - yes, web components can do all of that. The article nails that part. But that’s maybe 20% of why people use frameworks.
The other 80% is reactivity. Vue’s ref/computed/watch system tracks dependencies and updates the DOM automatically. With raw web components you’re back to manually querying elements and setting textContent every time state changes. You can build your own reactive layer on top, but at that point you’re just writing a framework with worse docs.
Same story with v-for, v-if, v-model, transitions, SSR, HMR, devtools, routing, state management. These aren’t nice-to-haves for real applications.
The “freedom from the upgrade treadmill” argument also cuts both ways. Yes, your web component won’t break on a major version bump. But you’ll spend that saved time writing boilerplate that frameworks handle in one line.

In my experience, web components can be inconsistent and cumbersome to implement well. They also introduce a potential single point of failure depending on how they’re integrated. That said, I’m not opposed to using them, I do understand their value and where they shine. I’d just advocate for using them deliberately and sparingly rather than as a replacement for a framework.

the biggest drawbacks of web component is not adopted is SSR.
and yeah SSR do matter.

I’m all for stability, but I wish web components had a little less boilerplate, you feel me? I might use this if I want to take my time in development, but I’d probably use Vue if I need to ship my website out to the world ASAP. I’ll still look into it though, looks promising.