The piece argues that claims about JavaScript frameworks being especially “agent-friendly” are often based on enthusiasm rather than evidence, and tests that idea with a small Pokémon catalog built from the PokéAPI. Opus 5.5 was given the same specification and asked to use one of 12 frameworks or approaches; each app was checked against a conformance suite, then compared on build cost, time, token use, code size, Lighthouse performance, and accessibility. The author ran five attempts per framework, generally using each framework’s official agent tools where available, while noting that both AI behavior and Lighthouse scores varied between runs.
Median build costs ranged from $2.67 for Hono with htmx to $4.97 for Angular. Astro, Hono with htmx, and Nuxt were among the quickest and least costly; SvelteKit, Gracile with Lit, and Angular cost more, partly because agents spent effort learning unfamiliar or newly changed tools. Angular also failed to produce a working app twice. Plain JavaScript with Vite was not automatically the cheapest or most effective option, underperforming several frameworks. The author stresses that this is a limited test of a relatively content-focused app, not a verdict for all software. Lighthouse tends to favor multi-page applications over single-page apps, and the supplied material describes the quality-testing method but does not include its results.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.