--- title: adam bien's blog | daily.dev description: Web frameworks were designed for human developers — readable abstractions, shared conventions, career value. AI coding agents have none of those needs. They... canonical: https://daily.dev/posts/adam-bien-s-blog-hd5kxt8ax 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: Web frameworks were designed for human developers — readable abstractions, shared conventions, career value. AI coding agents have none of those needs. They... og:url: https://daily.dev/posts/adam-bien-s-blog-hd5kxt8ax og:image: https://api.daily.dev/og/posts/Hd5kXt8ax.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 · 0 upvotes · 0 comments ## Summary Web frameworks were designed for human developers — readable abstractions, shared conventions, career value. AI coding agents have none of those needs. They don't benefit from abstractions meant to be read, and framework consistency is irrelevant when consistency comes from the agent's own skill. Writing directly against the web platform instead eliminates package.json, bundlers, transpilers, lockfiles, and postinstall scripts — all of which agents can silently manipulate without review. The platform gap is closing fast: custom elements power GitHub, YouTube, Photoshop on the web, SAP UI5, and Adobe Spectrum. React 19 even added proper custom element support. What frameworks still provide beyond standards is small: lit-html for templating, a simple unidirectional store for state. Widget libraries are still needed, but custom elements expose a stable, specified interface (attributes, properties, events, slots) that an agent can drive without versioned documentation — unlike React props that change between major versions. Platform code also outlives the conventions that produced it, making it more durable for agent-generated codebases. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why would an AI coding agent work better with native custom elements than with React components? Custom elements expose a specified interface of attributes, properties, events and slots, so an agent can determine the calling convention for an element it never saw during training. React components expose arbitrary props that change between major versions, meaning the agent needs correctly versioned documentation to drive them correctly, and platform code keeps running even if the conventions used to generate it change later. _Anyone weighing agent-driven frontend workflows can follow this web-platform-versus-framework debate on daily.dev._ ### Did React 19 add support for custom elements? Yes, React 19 added proper custom element support, which is framed as evidence that frameworks are moving toward the web platform rather than away from it, alongside efforts like the Interop project pushing framework ideas into browser specifications within a release cycle or two and Baseline tracking their availability across engines. _Track how framework and platform capabilities converge over time by following web platform news on daily.dev._ ## 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 - [Why AI hates modern web frameworks \(and loves web standards\)](https://daily.dev/posts/why-ai-hates-modern-web-frameworks-and-loves-web-standards--ywhpdjqhc) · Codemotion · 1 upvotes · 2 comments - [Web Components: The Framework-Free Renaissance](https://daily.dev/posts/web-components-the-framework-free-renaissance-lvucvixaf) · Hacker News · 65 upvotes · 5 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 · 7 upvotes · 0 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 --- Tags: [#webdev](https://daily.dev/tags/webdev), [#ai-agents](https://daily.dev/tags/ai-agents), [#web-components](https://daily.dev/tags/web-components) [View this post on daily.dev](https://daily.dev/posts/adam-bien-s-blog-hd5kxt8ax) ```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-hd5kxt8ax","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/adam-bien-s-blog-hd5kxt8ax"},"datePublished":"2026-08-09T16:52:41.230Z","dateModified":"2026-09-13T20:20:30.320Z","description":"Web frameworks were designed for human developers — readable abstractions, shared conventions, career value. AI coding agents have none of those needs. They...","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-hd5kxt8ax","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"webdev,ai-agents,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-hd5kxt8ax#faq","mainEntity":[{"@type":"Question","name":"Why would an AI coding agent work better with native custom elements than with React components?","acceptedAnswer":{"@type":"Answer","text":"Custom elements expose a specified interface of attributes, properties, events and slots, so an agent can determine the calling convention for an element it never saw during training. React components expose arbitrary props that change between major versions, meaning the agent needs correctly versioned documentation to drive them correctly, and platform code keeps running even if the conventions used to generate it change later. Anyone weighing agent-driven frontend workflows can follow this web-platform-versus-framework debate on daily.dev."}},{"@type":"Question","name":"Did React 19 add support for custom elements?","acceptedAnswer":{"@type":"Answer","text":"Yes, React 19 added proper custom element support, which is framed as evidence that frameworks are moving toward the web platform rather than away from it, alongside efforts like the Interop project pushing framework ideas into browser specifications within a release cycle or two and Baseline tracking their availability across engines. Track how framework and platform capabilities converge over time by following web platform news on daily.dev."}}]} ```