---
title: "adam bien's blog"
url: https://daily.dev/posts/adam-bien-s-blog-xwpi8mvva
source_url: https://adambien.blog/roller/abien/entry/with_llms_web_frameworks_become_irrelevant
type: article
source: "Adam Bien"
published: 2026-08-08T17:30:09.114Z
updated: 2026-08-08T17:30:37.369Z
tags: ["webdev", "javascript", "react", "llm", "web-components"]
reading_time: 3
upvotes: 2
comments: 0
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# adam bien's blog

**[Adam Bien](https://daily.dev/sources/adam-bien)** · 3 min read · 2 upvotes · 0 comments

## Summary

Adam Bien argues that web frameworks are becoming irrelevant due to two converging forces: LLM-powered agents that don't need human-readable abstractions or short learning curves, and the web platform itself closing the gap with native standards. Custom Elements, Shadow DOM, ES modules, import maps, Navigation API, CSS nesting, and other browser-native APIs now cover what frameworks were invented to provide. Agents generate boilerplate without needing framework conventions, and platform-native code doesn't break across major versions the way framework code does. The only remaining gap is interruptible rendering for very heavy UIs — a requirement most applications don't have.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://adambien.blog/roller/abien/entry/with_llms_web_frameworks_become_irrelevant>

## Questions this post answers

### What web platform APIs now replace the need for a JavaScript framework?

Custom Elements and Shadow DOM replace the component model; ES modules and import maps handle dependency resolution without a build step; the Navigation API and URLPattern cover routing; structuredClone() replaces Immer for immutable state; the dialog element, popover, and View Transitions handle overlays; CSS nesting, :has(), container queries, and cascade layers replace preprocessors. Baseline interop gets these into all three browser engines in months rather than years.

_Frontend developers navigating the framework-vs-platform decision track these spec milestones on daily.dev._

### Why would LLM coding agents make web frameworks less useful compared to vanilla web components?

LLM agents don't benefit from human-readable abstractions or short learning curves — the ergonomics frameworks provide are purely for human developers. Agents also add packages autonomously and faster than humans, making dependency auditing harder. Custom elements expose a stable, spec-defined interface of attributes, properties, events, and slots, so an agent knows the calling convention without versioned docs. React props change between major versions, requiring correctly versioned documentation to drive reliably.

_Teams deciding between framework-heavy and platform-native stacks for agent-assisted codebases find relevant takes on daily.dev._

## Similar posts on daily.dev

- [adam bien's blog](https://daily.dev/posts/adam-bien-s-blog-hd5kxt8ax) · Adam Bien · 0 upvotes · 0 comments
- [adam bien's blog](https://daily.dev/posts/adam-bien-s-blog-ymudertfm) · Jakarta EE · 1 upvotes · 0 comments
- [Anti-frameworkism: Choosing native web APIs over frameworks](https://daily.dev/posts/anti-frameworkism-choosing-native-web-apis-over-frameworks-4ybjlyvj3) · LogRocket · 2 upvotes · 0 comments

---

Tags: [#webdev](https://daily.dev/tags/webdev), [#javascript](https://daily.dev/tags/javascript), [#react](https://daily.dev/tags/react), [#llm](https://daily.dev/tags/llm), [#web-components](https://daily.dev/tags/web-components)

[View this post on daily.dev](https://daily.dev/posts/adam-bien-s-blog-xwpi8mvva)