Native browser APIs now provide powerful alternatives for routing, state management, and components. Never mind the frameworks, use the browser.

The New Stack is a publication covering trends and technologies in cloud-native development, DevOps, and software delivery. Developers can learn about containerization, Kubernetes, and cloud computing, as well as explore topics such as microservices architecture, serverless computing, and continuous integration/continuous delivery (CI/CD) pipelines.

The New Stack

Modern browsers now natively support features that once required frameworks like React and Angular. Native APIs for routing, state management, component isolation, and animations are reducing the need for heavy framework dependencies. While frameworks still offer value through conventions and ecosystem support, they're shifting from necessity to preference. Standards-based development using Shadow DOM, ES modules, Navigation API, and Web Components can deliver better performance with smaller bundle sizes, especially for mobile and edge computing environments. The web platform has matured enough to handle modern application development without framework intermediaries.

Stop Ignoring the Browser: The Biggest Frontend Shift in a Decade

Frameworks Were Always a Patch, Not a Cure

The Performance Argument: Native vs. Frameworks

I love it when web standards are pushed compared to pushing unnecessary bloat or libraries that are easily written yourself.
I however disagree with this post. Yes standards have improved drastically but the “web components” stuff is nowhere near as ergonomic as lets say React or Svelte.
What has improved and is still improving though is date stuff, url/location stuff, imports and exports and css features like container queries and :has(). But these features are not exclusive to web components and developers of framework using applications can benefit from them just as much.

This post has a point if you are creating a static website. however, for systems that contain backends and API calls. It goes boon… It’s a horror to manipulate the DOM.

This should be the case, the simple essentials must be done as some built in features, and not fully dependent on frameworks. There are much more advance features awaiting that a Framework should work on to resolve.

And the best WC framework is componentForge <a href="https://componentforge.collabmantra.com/" target="_blank" rel="noopener nofollow">https://componentforge.collabmantra.com/</a>

Call me old school… but I absolutely love simplicity.
I’ve been developing and shipping solutions for my paying clients using a stack of PHP, HTMX, AlpineJs and Tailscale…. 
I call it my PHAT stack. I’ve trained several AI agents to scaffold awesome foundations using it that get me right into the business logic.
I’m considering adding Astro to the stack, and I’ve swapped out Bootstrap for Tailwind… which is the beauty of it… you can roll your own solution based on the problem and the whole thing is lean and mean with minimal overhead. I hope PWA’s continue to evolve and that the browser unlocks more native tools in iOS and Android!