--- title: adam bien's blog | daily.dev description: Web frameworks were designed for human developers — readable abstractions, shared conventions, career value. But AI coding agents have none of those needs. An... canonical: https://daily.dev/posts/adam-bien-s-blog-ymudertfm 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. But AI coding agents have none of those needs. An... og:url: https://daily.dev/posts/adam-bien-s-blog-ymudertfm og:image: https://api.daily.dev/og/posts/yMuDERTFM.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 **[Jakarta EE](https://daily.dev/sources/jakartaee)** · 3 min read · 1 upvotes · 0 comments ## Summary Web frameworks were designed for human developers — readable abstractions, shared conventions, career value. But AI coding agents have none of those needs. An agent writing against the web platform directly can produce a list component in ~20 lines, ship without a package.json, bundler, or transpiler, and use an import map instead. This also eliminates lockfiles and transitive dependency graphs, which matter more with agents because package auditing is the first review step to disappear. The web platform is closing the gap with frameworks faster than ever: custom elements power GitHub, YouTube, Photoshop on the web, SAP UI5, and Adobe Spectrum. React 19 added proper custom element support, signaling frameworks moving toward the platform. For what standards don't cover, lit-html handles templating at a few KB and a simple unidirectional store handles state — neither locks the app in. Custom elements also expose a stable, specified interface (attributes, properties, events, slots) that an agent can drive without versioned documentation, unlike React props that shift between major versions. ## 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 prefer custom elements over 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 encountered during training. React components expose arbitrary props that change between major versions, requiring correctly versioned documentation for an agent to use them reliably, making the specified custom element interface a more stable target. _Developers weighing agent-friendly frontend architectures can find this kind of platform-versus-framework analysis on daily.dev._ ### Does React support custom elements natively? Yes, React 19 added proper custom element support, reflecting a broader trend of frameworks moving toward the web platform rather than away from it. This follows standards bodies absorbing ideas that originated in frameworks, with the Interop project pushing them into all three major browser engines within months, tracked via Baseline. _Track how frameworks like React align with platform standards by following updates on daily.dev._ ## Similar posts on daily.dev - [Web Components: The Framework-Free Renaissance](https://daily.dev/posts/web-components-the-framework-free-renaissance-lvucvixaf) · Hacker News · 65 upvotes · 5 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 - [The asteroid currently hitting frontend web development](https://daily.dev/posts/the-asteroid-currently-hitting-frontend-web-development-yg1hcgvqp) · Read the Tea Leaves · 38 upvotes · 7 comments - [Using Agentic AI to create your own component library](https://daily.dev/posts/using-agentic-ai-to-create-your-own-component-library-feei3hkq1) · Tim Deschryver · 0 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-ymudertfm) ```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-ymudertfm","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/adam-bien-s-blog-ymudertfm"},"datePublished":"2026-08-10T06:12:35.472Z","dateModified":"2026-09-13T20:44:58.723Z","description":"Web frameworks were designed for human developers — readable abstractions, shared conventions, career value. But AI coding agents have none of those needs. An...","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":"Jakarta EE","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":"Jakarta EE","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/5ef0720bb0684fa3ab12b4d4634f8028","url":"https://daily.dev/sources/jakartaee"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/adam-bien-s-blog-ymudertfm","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@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":"Jakarta EE","item":"https://daily.dev/sources/jakartaee"},{"@type":"ListItem","position":3,"name":"adam bien's blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/adam-bien-s-blog-ymudertfm#faq","mainEntity":[{"@type":"Question","name":"Why would an AI coding agent prefer custom elements over 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 encountered during training. React components expose arbitrary props that change between major versions, requiring correctly versioned documentation for an agent to use them reliably, making the specified custom element interface a more stable target. Developers weighing agent-friendly frontend architectures can find this kind of platform-versus-framework analysis on daily.dev."}},{"@type":"Question","name":"Does React support custom elements natively?","acceptedAnswer":{"@type":"Answer","text":"Yes, React 19 added proper custom element support, reflecting a broader trend of frameworks moving toward the web platform rather than away from it. This follows standards bodies absorbing ideas that originated in frameworks, with the Interop project pushing them into all three major browser engines within months, tracked via Baseline. Track how frameworks like React align with platform standards by following updates on daily.dev."}}]} ```