How we rebuilt Next.js with AI in one week

Technical approach & headline results

• Commenters see this as an expected but still striking milestone: given strong models, a clear API surface, and a large test suite, cloning a complex framework now looks feasible.
• Many note that the true heavy lifting is done by Vite and Next’s own tests; the LLM mainly acted as a translator/rewriter on top of that.
• Traffic-aware pre-rendering (using Cloudflare traffic analytics to selectively pre-render hot pages) is called out as the genuinely new idea, versus the rest being a reimplementation.

Skepticism about quality and “rebuilt in a week” framing

• Multiple people doubt “rebuilt from scratch” and “drop-in replacement” claims, especially given that even “hello world” reportedly fails in some cases.
• Concerns: missing edge cases, years of bug fixes not encoded in tests, and behavioral differences (e.g., forms, routing, server actions).
• Some see this as an AI-hype post similar to other recent “we built X with AI” announcements that didn’t fully work under scrutiny.

Open source, tests, and cloning incentives

• Strong tests and documentation are seen as a “spec” that makes cloning trivial; SQLite’s private test suite is cited as a counter-strategy.
• Debate over whether this is simply how open source is supposed to work vs. fear of large companies “yoinking” community work and undercutting smaller projects, including copyleft ones.

Next.js, Vercel, and vendor lock-in

• Many criticize Next.js as bloated, unstable across versions, tightly coupled to Vercel, and painful to self-host.
• Others defend its innovations (React Server Components, server actions) but dislike the pace and direction of changes.
• Some welcome vinext as a way to break the “Next.js/Vercel axis” and make migration to Cloudflare easier.

Cloudflare reception & credibility

• Several commenters complain about Cloudflare’s poor support, frequent outages, and a perceived decline in blog quality into “LLM slop.”
• There’s a pattern noted: splashy AI experiments (e.g., Matrix, now vinext) that feel half-baked and may not be maintained long-term.

Strategic implications & developer impact

• Astro’s recent acquisition plus this project is interpreted as a signal that framework lock-in is weakening; Cloudflare wants to host whatever you already use.
• Some developers are uneasy about the blog’s tone—implicitly devaluing years of work by the Next.js team and, by extension, software engineers generally.
• Others see this as proof that a certain class of porting/rewriting work is now cheap if you have good tests, possibly heralding a resurgence of test-driven development.