How we rebuilt Next.js with AI in one week

Post by boarush » Wed, Feb 25, 2026, 12:58 PM UTC

TonyStr wrote: post #178

ZebulonP wrote: post #147

Earlier quoted context omitted.

(to be transparent - I'm a Cloudflare engineer) The behavior isn't entirely the same and reaching 100% parity is a non-goal, but there are a few things to note. This is still a very early implementation and there are undoubtedly issues with the implementation that weren't covered in next's original test suite (and thus not inherited) while not being obvious enough to pop up with all the apps we've tried so far. As fo…

Why is parity a non-goal? The blog post states: > The result, vinext (pronounced "vee-next"), is a drop-in replacement for Next.js "Drop-in" in my mind means I can swap the next dependency for the vinext dependency and my app will function the same. If the reality is that I have to spend hours or days debugging obscure edge cases that appear in vinext, I wouldn't exactly call that a drop-in replacement. I understand…

Post by ryanmcl » Wed, Feb 25, 2026, 1:11 PM UTC

Zanfa wrote: post #171

neya wrote: post #128

Earlier quoted context omitted.

If Rails is considered a worse framework, then I'm pretty much speechless. Not everything has to be about performance. Security is a thing too.

I miss Rails so much when working with any of the top JS frameworks. Every time I run into an issue that Rails had a standardized solution for a decade ago just proves that most of the JS world spends their days metaphorically digging holes with sharp sticks, rather than using the appropriate tool. But the industry values overpaying stick-diggers over results, therefore I gotta play along…

Post by meiuqer » Wed, Feb 25, 2026, 1:25 PM UTC

mikestorrent wrote: post #106

thousand_nights wrote: post #33

Earlier quoted context omitted.

at my job we have some 7+ year old nextjs apps that don't receive new features but still do their jobs perfectly fine, and they keep changing random shit around for no reason, we've had to waste time on multiple refactors already for major nextjs version bumps once the older ones are no longer supported

Is there any front end framework that doesn't do this? I dropped out of the front end years ago, and it seems to just get worse every year with a profusion of confusion. Doesn't anyone yearn for back when we didn't have to build the front end at all?? Just emit some HTML and serve up some JS files from the backend, and everything just flows from there? Someone go make an AI rewrite of Apache+Mod-PHP and sell it to zo…

Post by orangecoffee » Wed, Feb 25, 2026, 2:00 PM UTC

adithyassekhar wrote: post #165

thkahfg wrote: post #154

Earlier quoted context omitted.

Clownflare engineers are in the chat now doing damage control and downvote opposition. Soon jgrahamc will appear and whitewash the theft.

It's wild. If I need to steal someone's code, I just need to let an ai crawl it and it'll regurgitate the same thing. I can't wait for it to recreate marvel movies.

Post by Zanfa » Wed, Feb 25, 2026, 2:09 PM UTC

Martinsos wrote: post #177

Zanfa wrote: post #171

Earlier quoted context omitted.

I miss Rails so much when working with any of the top JS frameworks. Every time I run into an issue that Rails had a standardized solution for a decade ago just proves that most of the JS world spends their days metaphorically digging holes with sharp sticks, rather than using the appropriate tool. But the industry values overpaying stick-diggers over results, therefore I gotta play along…

Shilling a bit but maybe check out wasp.sh, we are conceptually very similar to "Rails for JS"! Just don't tell Claude to completely copy us hehe (pls)