--- title: The asteroid currently hitting frontend web development description: A veteran frontend performance writer reflects on how AI coding agents are reshaping frontend web development, noting that many well-known frontend educators... canonical: https://daily.dev/posts/the-asteroid-currently-hitting-frontend-web-development-yg1hcgvqp twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The asteroid currently hitting frontend web development | daily.dev og:description: A veteran frontend performance writer reflects on how AI coding agents are reshaping frontend web development, noting that many well-known frontend educators... og:url: https://daily.dev/posts/the-asteroid-currently-hitting-frontend-web-development-yg1hcgvqp og:image: https://api.daily.dev/og/posts/yG1hcgVQp.png og:image:alt: The asteroid currently hitting frontend web development 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. # The asteroid currently hitting frontend web development **[Read the Tea Leaves](https://daily.dev/sources/nolanlawson)** · 13 min read · 38 upvotes · 7 comments ## Summary A veteran frontend performance writer reflects on how AI coding agents are reshaping frontend web development, noting that many well-known frontend educators are pivoting away from the field or quitting entirely. The author demonstrates that Claude Sonnet can already give expert-level CSS performance debugging advice, and argues frontend code is riskier to hand fully to agents than backend code because it's more ephemeral and replaceable. Trends discussed include companies like Cursor and Viget migrating from Solid/Lit back to React because 'agents know React' better, developer experience mattering less since agents don't need ergonomic APIs, and web standards work shifting away from syntax ergonomics toward capabilities. The piece suggests future opportunities may lie in agent-optimized websites, MPA frameworks like Astro, and consulting to fix 'vibe-coded' production sites, while expressing genuine uncertainty and gloom about the field's trajectory. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why are companies migrating their frontend codebases from Solid or Lit to React even though those frameworks are more performant? Companies like Cursor and Viget have migrated from Solid and Lit to React because AI coding agents are far more proficient with React, which dominates the training data used by large language models. Even though frameworks like Solid offer better performance and less code, 'agent experience' is starting to matter more than traditional developer experience, since agents struggle to write idiomatic code in less common frameworks. _Developers weighing framework migrations amid AI-driven tooling shifts can track this debate on daily.dev._ ### What should I check in a Chrome performance trace when Style Calculation cost is high but Layout cost is low? High Style cost with low Layout cost usually means selector matching and invalidation are expensive, not geometry changes. Check selector complexity, invalidation scope (a class toggle high in the DOM can force recalculation on large subtrees), inherited property changes like font-size or CSS custom properties on a shared ancestor, and shadow DOM component boundaries. Chrome DevTools' 'Selector Stats' feature shows which selectors are slow and how many elements they matched. _Frontend engineers debugging style recalculation costs can follow CSS performance discussions on daily.dev._ ### Should I use an SPA framework like React or an MPA framework like Astro for a marketing website built with AI coding agents? An MPA framework such as Astro or Eleventy is often the better choice for marketing sites, even when using AI agents, because it requires roughly 50% less code than a full SPA and avoids common SPA pitfalls like broken back-button behavior, focus state issues, and performance problems. Agents tend to default to writing React SPAs, but that doesn't mean an SPA is the right architectural choice. _Teams deciding between SPA and MPA architectures for AI-assisted projects can weigh trade-offs via daily.dev._ ## Community take How the wider developer community reacted, aggregated from 5 discussions and 305 comments across lobsters, hackernews (as of 2026-09-14). **TL;DR:** The thread mostly drifts away from the article itself into a sprawling debate about whether AI can replace paid web/software development work, with strong disagreement over whether AI-built sites and tools are viable long-term or just short-term slop; a smaller side-thread specifically engages the article's claim that frontend is lower-risk to hand to agents than backend. **Sentiment:** 30% positive · 45% mixed · 25% skeptical **The case for** - Non-technical people can now produce usable websites and internal tools themselves at near-zero cost using AI, citing real examples (a biotech co-founder's wife, a psychology practice site). - Some argue frontend genuinely is a good target for agents because visual bugs are easy to spot and code is cheap to redo, unlike backend logic. - AI lets experienced developers iterate quickly and rebuild/replace SaaS-style tools tailored to their exact workflow for a fraction of the cost. **The pushback** - Vibe-coded sites and tools are seen as risky technical debt that will likely need expensive consultants to fix or replace later, especially for regulated/financial use cases needing audits and compliance. - Frontend code can still be invisibly broken (e.g. complex state bugs in SPAs), contradicting the article's framing that frontend failures are always visible. - LLMs still struggle with visual/design taste and 'feel' (animations, UX polish), producing recognizably AI-flavored, homogenized output that some find creatively stale. - Heavy AI reliance risks a broader homogenization of tools/frameworks (e.g. React dominance) and long-term knowledge/quality erosion across the web. **By community** - lobsters (mixed): No comments were provided, so sentiment can't be assessed beyond the modest point count. - hackernews (heated): A long, contentious back-and-forth pits AI-optimism (agents already replacing paid dev/design work) against skepticism about technical debt, compliance risk, and whether frontend bugs are really as 'visible' as the article claims. **Hottest debate:** Whether AI-generated ('vibe-coded') sites and internal tools are a genuine cost-saving win or just cheap-looking technical debt that will need expensive professional cleanup later, especially in regulated domains like finance. **Open questions** - Will there be a sustained consulting market for fixing vibe-coded production sites, and how soon? - Can AI coding agents ever develop real visual/UX taste, or will output stay recognizably homogenized and 'AI-flavored'? - How will framework homogenization (agents favoring React) affect innovation in web frameworks long-term? **Highlights** > > you don't need a $5m/yr salesforce / servicenow contract when you understand the business model I'm sure many people will think that; and I'm also fairly confident that 5 years later they'll take their obscure, bug-ridden, vibecoded monstrosity that nobody really understands, throw it out, and get a salesforce contract. Technical debt doesn't disappear just because you have agents working for you; in fact, it is exploding right now, and I would bet good money that 2-3 years for now there will be a flourishing cottage industry of consultancies specialized in dealing with such monstrosities. > — [toyg on hackernews · 1 comments](https://news.ycombinator.com/item?id=49557569) > Frontend development - perhaps more than any other kind of software development - is “what you see is what you get”. There aren’t a lot of ways a website can be invisibly broken. Systems engineering isn’t like that. Vibe coders beware: A database could silently corrupt data, or have latent security vulnerabilities. It might have a badly designed query language that will be difficult to change later. But frontend code can be rewritten at will. It’s a perfect target for LLMs. > — [josephg on hackernews · 5 comments](https://news.ycombinator.com/item?id=49557707) > "There aren’t a lot of ways a website can be invisibly broken." ??? Have you never debugged weird react state before??? Have you never used a nontrivial SPA before? Even the most simple react SPA has about a trillion states. I don't really know how to respond to your statement than "no, they can definitely be invisibly broken." > — [atomicnumber3 on hackernews · 2 comments](https://news.ycombinator.com/item?id=49559153) > At the same time I have found LLMs far less competent at frontend because they don't seem to have any visual understanding of what a good website looks like. > — [Gigachad on hackernews · 1 comments](https://news.ycombinator.com/item?id=49558346) > > For better or worse, React is heavily overrepresented in the training weights, and “agent experience” is starting to matter more than developer experience. Another winner takes all situation. This and the other post on agent tool use[1] makes me think we are in a period of great homogenization. I'm sure there's a group that's delighted about this but for me, it just makes me feel a little uneasy. [1] https://armature.tech/blog/which-tools-coding-agents-install > — [chanux on hackernews · 6 comments](https://news.ycombinator.com/item?id=49560337) **Source threads** - [lobsters](https://lobste.rs/s/rntyvm/asteroid_currently_hitting_frontend_web) · 11 points · 2 comments - [hackernews](https://news.ycombinator.com/item?id=49555233) · 99 points · 288 comments - [hackernews](https://news.ycombinator.com/item?id=49520616) · 23 points · 14 comments - [hackernews](https://news.ycombinator.com/item?id=49418204) · 19 points · 0 comments - [hackernews](https://news.ycombinator.com/item?id=49413685) · 9 points · 1 comments ## Community discussion Top comments from developers on daily.dev. **@jataki** · 15 upvotes > I am not sure what to feel about this article - most (if not all) of the points apply to virtually any other field? So what, let's get rid of teachers then? A bit silly if you ask me. > > > There is also this absurd claim and notion that frontend is easier for agents than backend. I couldn't disagree more. Backend is much riskier in the sense that any damage you do to your system can be permanent. But one could also argue that your frontend and user experience, while more ephemeral, has a much bigger impact on your brand. Backend is logical and follows an expected path that is easy for an agent... **@fabianletsch** · 4 upvotes > All I can say is that in the AI company that I am working at, my Frontend skills are very much wanted and needed and I use coding agents a lot for my work but there are things where my personal extensive knowledge and gut feelings are able to solve issues that the coding agents with a very good harness cannot. > > > Most of the time its both though. I am often surprised by the things its doing, that I would have forgotten or done worse. **@springtofigh** · 4 upvotes > I really hope this AI coding trend in front-end goes away! It's very exhausting that everywhere I go on social media, people talk about it without anyone caring about real programming knowledge. Everywhere, it's all about prompts, AI agents, context engineering, and so on. It has created a very tough environment for junior developers. I'm very glad that I didn't start in the front-end field during this time. **@softwareengineering1** · 1 upvotes > Spot on analysis! We are shifting from writing repetitive boilerplate to becoming system architects and prompt directors. The point about agents 'knowing React better' is particularly fascinating—ecosystem dominance might soon be driven by AI training data rather than human developer ergonomics. The future belongs to those who focus on core architecture, web capabilities, and bridging the gaps of AI-generated code. **@mishatvoy** · 0 upvotes > I don’t think this means the end of frontend, but rather another step in its evolution. We’ve already gone from vanilla JS to jQuery and then to modern frameworks. This time the shift is just much bigger and affects more people at once > > Remember the Web3 hype? Everyone was saying it would replace Web2, but eventually it settled into a niche. I think AI will be similar in that regard: the hype will cool down, but the technology itself will stay and become a normal part of our lives. Simply because it has a much broader range of applications ## Similar posts on daily.dev - [10 anti-AI slop moves for frontend projects going faster than humans can review—Martian Chronicles, Evil Martians’ team blog](https://daily.dev/posts/10-anti-ai-slop-moves-for-frontend-projects-going-faster-than-humans-can-review-martian-chronicles--70jbo6jvx) · Martian Chronicles · 24 upvotes · 5 comments - [The winners and losers of AI coding](https://daily.dev/posts/the-winners-and-losers-of-ai-coding-c9g8tiwqf) · InfoWorld · 0 upvotes · 0 comments - [The AI Tools Every Frontend Developer Should Know in 2026](https://daily.dev/posts/the-ai-tools-every-frontend-developer-should-know-in-2026-k0zqq7t37) · Medium · 1 upvotes · 0 comments - [How Do We Write About AI in Web Development?](https://daily.dev/posts/how-do-we-write-about-ai-in-web-development--ojp4dot7u) · Cloud Four · 4 upvotes · 0 comments - [Issue \#755: The asteroid hitting frontend development — Frontend Focus](https://daily.dev/posts/issue-755-the-asteroid-hitting-frontend-development-frontend-focus-mu1e0hypu) · Frontend Focus · 4 upvotes · 0 comments --- Tags: [#webdev](https://daily.dev/tags/webdev), [#react](https://daily.dev/tags/react), [#css](https://daily.dev/tags/css) [View this post on daily.dev](https://daily.dev/posts/the-asteroid-currently-hitting-frontend-web-development-yg1hcgvqp) ```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":"The asteroid currently hitting frontend web development","url":"https://daily.dev/posts/the-asteroid-currently-hitting-frontend-web-development-yg1hcgvqp","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-asteroid-currently-hitting-frontend-web-development-yg1hcgvqp"},"datePublished":"2026-08-23T23:55:28.589Z","dateModified":"2026-09-14T06:55:23.729Z","description":"A veteran frontend performance writer reflects on how AI coding agents are reshaping frontend web development, noting that many well-known frontend educators...","image":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","thumbnailUrl":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","isAccessibleForFree":true,"articleSection":"Read the Tea Leaves","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":"Read the Tea Leaves","logo":"https://media.daily.dev/image/upload/s--hCPaPAOM--/f_auto/v1727446484/logos/nolanlawson","url":"https://daily.dev/sources/nolanlawson"},"commentCount":7,"discussionUrl":"https://daily.dev/posts/the-asteroid-currently-hitting-frontend-web-development-yg1hcgvqp","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":38},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":7}],"keywords":"webdev,react,css","timeRequired":"PT13M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Read the Tea Leaves","item":"https://daily.dev/sources/nolanlawson"},{"@type":"ListItem","position":3,"name":"The asteroid currently hitting frontend web development"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/the-asteroid-currently-hitting-frontend-web-development-yg1hcgvqp","comment":[{"@type":"Comment","text":"I am not sure what to feel about this article - most (if not all) of the points apply to virtually any other field? So what, let’s get rid of teachers then? A bit silly if you ask me.\nThere is also this absurd claim and notion that frontend is easier for agents than backend. I couldn’t disagree more. Backend is much riskier in the sense that any damage you do to your system can be permanent. But one could also argue that your frontend and user experience, while more ephemeral, has a much bigger impact on your brand. Backend is logical and follows an expected path that is easy for an agent to understand; frontend is visual and much more difficult for it to comprehend.\nAnyone claiming this hasn’t tried building both sides with an agent.","datePublished":"2026-08-24T20:28:31.757Z","url":"https://daily.dev/posts/yG1hcgVQp#c-MW0f8CUjr","author":{"@type":"Person","name":"Manu","url":"https://daily.dev/jataki","image":"https://media.daily.dev/image/upload/s--ZkGZoSg9--/f_auto/v1786360868/avatars/avatar_boM1zeIEEMcERdMpasALr?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":15}},{"@type":"Comment","text":"All I can say is that in the AI company that I am working at, my Frontend skills are very much wanted and needed and I use coding agents a lot for my work but there are things where my personal extensive knowledge and gut feelings are able to solve issues that the coding agents with a very good harness cannot.\nMost of the time its both though. I am often surprised by the things its doing, that I would have forgotten or done worse.","datePublished":"2026-08-25T11:43:10.421Z","url":"https://daily.dev/posts/yG1hcgVQp#c-w8V7ex3Xh","author":{"@type":"Person","name":"Fabian Letsch","url":"https://daily.dev/fabianletsch","image":"https://lh3.googleusercontent.com/a/ACg8ocKR6BVy_wn23EoOKq7-BlszlcXcLmASlnb7l-GtS-q1bePnkaJf=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":4}},{"@type":"Comment","text":"I really hope this AI coding trend in front-end goes away! It’s very exhausting that everywhere I go on social media, people talk about it without anyone caring about real programming knowledge. Everywhere, it’s all about prompts, AI agents, context engineering, and so on. It has created a very tough environment for junior developers. I’m very glad that I didn’t start in the front-end field during this time.","datePublished":"2026-08-25T11:14:30.049Z","dateModified":"2026-08-25T11:14:53.891Z","url":"https://daily.dev/posts/yG1hcgVQp#c-gxK4HmE1U","author":{"@type":"Person","name":"Spring Tofigh","url":"https://daily.dev/springtofigh","image":"https://avatars.githubusercontent.com/u/90114320?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":4}},{"@type":"Comment","text":"Spot on analysis! We are shifting from writing repetitive boilerplate to becoming system architects and prompt directors. The point about agents ‘knowing React better’ is particularly fascinating—ecosystem dominance might soon be driven by AI training data rather than human developer ergonomics. The future belongs to those who focus on core architecture, web capabilities, and bridging the gaps of AI-generated code.","datePublished":"2026-08-25T04:34:25.493Z","url":"https://daily.dev/posts/yG1hcgVQp#c-GfX7JXF2d","author":{"@type":"Person","name":"Softwareengineering","url":"https://daily.dev/softwareengineering1","image":"https://media.daily.dev/image/upload/s--o6rMKZ2X--/f_auto/v1785935124/avatars/avatar_W6Yq6NMdsZDHQa2S3qYON?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}},{"@type":"Comment","text":"I don’t think this means the end of frontend, but rather another step in its evolution. We’ve already gone from vanilla JS to jQuery and then to modern frameworks. This time the shift is just much bigger and affects more people at once\nRemember the Web3 hype? Everyone was saying it would replace Web2, but eventually it settled into a niche. I think AI will be similar in that regard: the hype will cool down, but the technology itself will stay and become a normal part of our lives. Simply because it has a much broader range of applications","datePublished":"2026-08-26T10:16:53.202Z","url":"https://daily.dev/posts/yG1hcgVQp#c-cQPvI3KFM","author":{"@type":"Person","name":"Mikhail","url":"https://daily.dev/mishatvoy","image":"https://avatars.githubusercontent.com/u/74988200?v=4"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-asteroid-currently-hitting-frontend-web-development-yg1hcgvqp#faq","mainEntity":[{"@type":"Question","name":"Why are companies migrating their frontend codebases from Solid or Lit to React even though those frameworks are more performant?","acceptedAnswer":{"@type":"Answer","text":"Companies like Cursor and Viget have migrated from Solid and Lit to React because AI coding agents are far more proficient with React, which dominates the training data used by large language models. Even though frameworks like Solid offer better performance and less code, 'agent experience' is starting to matter more than traditional developer experience, since agents struggle to write idiomatic code in less common frameworks. Developers weighing framework migrations amid AI-driven tooling shifts can track this debate on daily.dev."}},{"@type":"Question","name":"What should I check in a Chrome performance trace when Style Calculation cost is high but Layout cost is low?","acceptedAnswer":{"@type":"Answer","text":"High Style cost with low Layout cost usually means selector matching and invalidation are expensive, not geometry changes. Check selector complexity, invalidation scope (a class toggle high in the DOM can force recalculation on large subtrees), inherited property changes like font-size or CSS custom properties on a shared ancestor, and shadow DOM component boundaries. Chrome DevTools' 'Selector Stats' feature shows which selectors are slow and how many elements they matched. Frontend engineers debugging style recalculation costs can follow CSS performance discussions on daily.dev."}},{"@type":"Question","name":"Should I use an SPA framework like React or an MPA framework like Astro for a marketing website built with AI coding agents?","acceptedAnswer":{"@type":"Answer","text":"An MPA framework such as Astro or Eleventy is often the better choice for marketing sites, even when using AI agents, because it requires roughly 50% less code than a full SPA and avoids common SPA pitfalls like broken back-button behavior, focus state issues, and performance problems. Agents tend to default to writing React SPAs, but that doesn't mean an SPA is the right architectural choice. Teams deciding between SPA and MPA architectures for AI-assisted projects can weigh trade-offs via daily.dev."}}]} ```