--- title: "adam bien's blog" url: https://daily.dev/posts/adam-bien-s-blog-hd5kxt8ax source_url: https://adambien.blog/roller/abien/entry/smalltalk_blocks_and_the_origins_of_eclipse_collections_airhacks_fm_podcast type: article source: "Adam Bien" published: 2026-08-09T16:52:41.230Z updated: 2026-08-09T16:53:11.438Z tags: ["webdev", "ai-agents", "web-components"] reading_time: 3 upvotes: 0 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 · 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 prefer web components and the native platform over React or Angular? Frameworks like React and Angular were designed for human readability, shared conventions, and career value — none of which apply to agents. The web platform eliminates package.json, bundlers, transpilers, and lockfiles that agents can silently modify. Custom elements expose a stable, specified interface (attributes, properties, events, slots) an agent can drive without versioned documentation, whereas React props change between major versions and require correctly versioned docs. _Teams shipping agent-generated frontends track this platform-vs-framework debate on daily.dev._ ### What real-world applications use custom elements in production? Custom elements carry the interfaces of GitHub, YouTube, Photoshop on the web, SAP UI5, and Adobe Spectrum. React 19 added proper custom element support, signaling that major frameworks are moving toward the platform rather than away from it. The Interop project and Baseline tracking get new web standards into all three browser engines in months rather than years. _Developers choosing between custom elements and component frameworks find the latest ecosystem moves on daily.dev._ ## Similar posts on daily.dev - [adam bien's blog](https://daily.dev/posts/adam-bien-s-blog-ymudertfm) · Jakarta EE · 1 upvotes · 0 comments - [adam bien's blog](https://daily.dev/posts/adam-bien-s-blog-xwpi8mvva) · Adam Bien · 2 upvotes · 0 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)