First screen, captured 1 day ago. Hover to scroll the page, or open the video.

The AI cost of JavaScript frameworks

What HN thinks

A benchmark about Pokémon apps somehow reignited the decade-old war over whether anyone can write vanilla JavaScript.

Frameworks are unnecessary overhead
Several argue vanilla JS, server rendering or HTMX suffice for most sites, especially now that agents write the code, and frameworks mainly serve hiring convenience.
Frameworks earn their keep in complex apps
Others counter that real commercial apps with heavy interactivity turn into spaghetti without a framework, and that outsourced maintenance and LLM familiarity with React are real benefits.
Benchmark too simple to judge
Many note the test app was a trivial content site, so results favour Astro and HTMX and say little about complex, interactive applications.

Consensus: Most agree the right choice depends on how interactive the app is, and that a more complex benchmark is needed before drawing strong conclusions.

Recommended in the comments

Astro (library): Topped the benchmark and users praise its pleasant experience and escape hatches.
htmx (library): Simple model that commenters find easy for both humans and agents on server-rendered sites.
Mithril ↗ (library): One commenter modernised it with agents, adding signals, typing and SSR, and fans find it token-efficient.
SvelteKit (library): Praised for fast agent-assisted development and progressive enhancement.
Nuxt (library): Clear docs and readable patterns make it easy for both people and LLMs.
SolidStart (library): Recommended for elegant handling of async, errors and concurrency in interactive apps.

Summarised by Claude from the comment thread 21 hours ago.

Points: 436
Comments: 325
Best rank: #3
Posted: 2026-11-01 by luu
Category: Web dev

javascript-frameworks ai-coding-agents benchmarks claude-code react sveltekit angular lighthouse

All captures:

Full page

Captured 1 day ago. Click for the whole screenshot.

Looks similar

Screenshot of nolanlawson.com: Skeptical of rewriting JavaScript tools in "faster" languages

Skeptical of rewriting JavaScript tools in "faster" languages (nolanlawson.com)

127 points by todsacerdoti 2 years ago | 219 comments

Screenshot of nolanlawson.com: Why do browsers throttle JavaScript timers?

Why do browsers throttle JavaScript timers?(nolanlawson.com)

52 points by vidyesh 1 year ago | 31 comments

Screenshot of nolanlawson.com: The asteroid currently hitting front end web development

The asteroid currently hitting front end web development (nolanlawson.com)

173 points by codechicago277 1 month ago | 207 comments

Screenshot of nolanlawson.com: AI Tribalism

AI Tribalism (nolanlawson.com)

37 points by zurvanist 9 months ago | 36 comments

Screenshot of nolanlawson.com: We mourn our craft

We mourn our craft (nolanlawson.com)

634 points by ColinWright 8 months ago | 737 comments

Nolan Lawson's blog post lamenting how AI coding tools are reducing programmers to code reviewers and mourning the loss of the programming craft.

ai-coding software-engineering programming-craft llms

Screenshot of nolanlawson.com: Using AI to write better code more slowly

Using AI to write better code more slowly (nolanlawson.com)

1102 points by signa11 5 months ago | 407 comments

Blog post by Nolan Lawson arguing that LLMs can be used to write higher-quality code more slowly, such as finding bugs, rather than producing low-quality code fast.

ai-coding llm code-quality software-engineering