The AI cost of JavaScript frameworks

The thread treated the article less as a verdict on web frameworks than as a test of what makes AI-assisted coding cheap, reliable, and maintainable. Several readers liked the evidence that a low-JavaScript, content-oriented approach can sharply reduce agent time and token spend; Astro in particular looked attractive for the narrow kind of site tested. Others argued that this is exactly why the ranking cannot be generalized: a small content app says little about real-time interactions, dense form validation, or larger long-lived products. A strong anti-framework current held that agents benefit from plain browser APIs, small bundles, and fewer dependencies because there is less code and abstraction to fit into context. But practical experience pushed back. One reader found that an agent handled a complicated stateful UI poorly in HTMX until extensive tests constrained it, while React was expected to model that job more naturally. Another warned that agent-generated vanilla front ends can collapse into enormous mixed HTML, CSS, and JavaScript files, making later edits slow and fragile unless a framework imposes structure. Commenters also objected to treating dollar cost and completion time as the only meaningful outputs. They stressed that tests, existing codebases, security history, domain fit, and whether humans can still reason about the result may justify modest extra AI cost. The broad conclusion was not that one framework won, but that AI changes the tradeoffs and makes task-specific evaluation essential.