<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/adam-bien-s-blog-xwpi8mvva" -->

---
title: adam bien's blog | daily.dev
description: 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...
canonical: https://daily.dev/posts/adam-bien-s-blog-xwpi8mvva
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: adam bien's blog | daily.dev
og:description: 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...
og:url: https://daily.dev/posts/adam-bien-s-blog-xwpi8mvva
og:image: https://api.daily.dev/og/posts/XWPi8MvVa.png
og:image:alt: adam bien's blog
og:image:width: 1200
og:image:height: 630
og:locale: 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 native browser APIs can replace common web framework features without a build step?

Custom Elements and Shadow DOM provide the component model, ES modules with import maps handle dependency resolution, structuredClone() replaces libraries like Immer for immutable updates, the Navigation API and URLPattern handle routing, and native dialog/popover plus View Transitions cover overlays and animated view changes.

_daily.dev surfaces platform-standard alternatives for developers weighing framework versus native web APIs._

### Why are custom elements considered better suited for AI coding agents than React components?

A custom element exposes attributes, properties, events, and slots through a specified interface, so an agent can infer the calling convention even for an element it never encountered during training. A React component exposes arbitrary props that change between major versions, requiring correctly versioned documentation for an agent to use it reliably.

_Developers building agent-friendly frontends can track this interface debate on daily.dev._

### What is the one remaining gap where web frameworks still outperform native browser primitives?

Interruptible rendering for very heavy UIs remains a gap: the platform primitives for it exist, but coordinating them requires manual work rather than an automated scheduler. Applications without that specific requirement, which covers most applications, no longer need to start with a framework for this reason.

_daily.dev helps engineers weigh trade-offs like rendering coordination when picking a frontend approach._

## Similar posts on daily.dev

- [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
- [Web Components: The Framework-Free Renaissance](https://daily.dev/posts/web-components-the-framework-free-renaissance-lvucvixaf) · Hacker News · 65 upvotes · 5 comments
- [Web Components Are the Comeback Nobody Saw Coming](https://daily.dev/posts/web-components-are-the-comeback-nobody-saw-coming-5oxazwtym) · The New Stack · 109 upvotes · 13 comments
- [Why don’t more developers “use the platform”?](https://daily.dev/posts/why-don-t-more-developers-use-the-platform--oagqrhfde) · Read the Tea Leaves · 6 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)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"adam bien's blog","url":"https://daily.dev/posts/adam-bien-s-blog-xwpi8mvva","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/adam-bien-s-blog-xwpi8mvva"},"datePublished":"2026-08-08T17:30:09.114Z","dateModified":"2026-09-14T06:05:12.478Z","description":"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...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d365e8cabb5d95ba36aaa092c23f211d?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/d365e8cabb5d95ba36aaa092c23f211d?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Adam Bien","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Adam Bien","logo":"https://media.daily.dev/image/upload/s--CInnAL-q--/f_auto,q_auto/v1773644276/logos/adam-bien?_a=BAMAMiiu0","url":"https://daily.dev/sources/adam-bien"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/adam-bien-s-blog-xwpi8mvva","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"webdev,javascript,react,llm,web-components","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Adam Bien","item":"https://daily.dev/sources/adam-bien"},{"@type":"ListItem","position":3,"name":"adam bien's blog"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/adam-bien-s-blog-xwpi8mvva#faq","mainEntity":[{"@type":"Question","name":"What native browser APIs can replace common web framework features without a build step?","acceptedAnswer":{"@type":"Answer","text":"Custom Elements and Shadow DOM provide the component model, ES modules with import maps handle dependency resolution, structuredClone() replaces libraries like Immer for immutable updates, the Navigation API and URLPattern handle routing, and native dialog/popover plus View Transitions cover overlays and animated view changes. daily.dev surfaces platform-standard alternatives for developers weighing framework versus native web APIs."}},{"@type":"Question","name":"Why are custom elements considered better suited for AI coding agents than React components?","acceptedAnswer":{"@type":"Answer","text":"A custom element exposes attributes, properties, events, and slots through a specified interface, so an agent can infer the calling convention even for an element it never encountered during training. A React component exposes arbitrary props that change between major versions, requiring correctly versioned documentation for an agent to use it reliably. Developers building agent-friendly frontends can track this interface debate on daily.dev."}},{"@type":"Question","name":"What is the one remaining gap where web frameworks still outperform native browser primitives?","acceptedAnswer":{"@type":"Answer","text":"Interruptible rendering for very heavy UIs remains a gap: the platform primitives for it exist, but coordinating them requires manual work rather than an automated scheduler. Applications without that specific requirement, which covers most applications, no longer need to start with a framework for this reason. daily.dev helps engineers weigh trade-offs like rendering coordination when picking a frontend approach."}}]}
```

