Live data from Hacker News

How we rebuilt Next.js with AI in one week

blog.cloudflare.com

131–140 of 252 posts

Re: How we rebuilt Next.js with AI in one week

#131
post #128
post #45

Earlier quoted context omitted.

Next is the worst framework I’ve ever used next to rails. It’s pure overhead for most apps.

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.

Rails powers nearly 15 percent of the US e-commerce. I love it. Any time I have to use another framework it feels like a huge downgrade. Rails has so many things that make it nice to use

Re: How we rebuilt Next.js with AI in one week

#132

[flagged]

> Surprised this didn't get a higher placement on the HN front page, only 34 points?

Vercel may be bad, but they have been a net positive to the web landscape, so many projects are alive because of them. And I truly respect the hard work the next devs put into their code and test suites. I'm surprised any self respecting dev even votes this up.

Re: How we rebuilt Next.js with AI in one week

#133

Earlier quoted context omitted.

> There's no way Cloudflare could have pulled this off without next's very own tests. I'm very uncovinced. History showed us very complex systems reverse engineered without access to the source code. With access to the source code, coupled with the rapid iteration of AI, I don't see any real moat here; at best a slight delay.

I have tried to post this here but it has not got traction. I have a demonstrated process here on my blog (all hand written without AI). This bit about how to brute force decompilation: https://reorchestrate.com/posts/your-binary-is-no-longer-saf... And this about how to do the conversion and address the LLM hallucination problem: https://reorchestrate.com/posts/your-binary-is-no-longer-saf... Yes, it is absolutely p…

There was a recent post on here where the creator of Ladybird (Andreas Kling) translated a chunk of his novel browser from c++ to Rust in two weeks -- a feat he estimated would take him months: https://ladybird.org/posts/adopting-rust/

I, in my own way, have discovered that recent versions of Claude are extremely (as in, super-humanly) good at rewriting or porting. Apparently if recently released coding agents have a predefined target and a good test suite then you can basically tell them that you want X (well-defined target w/ good suite of tests) written in Y (the language/framework you want X written in but it isn't) -- and a week or two later you have a working version.

I have spent the last month wrapping my head around the idea that there is a class of tasks in software engineering that is now solved for not very much money at all. More or less every single aspirational idea I have ever had over the last 20 years or so I have begun emabarking on within the last two months.

I hear you.

Re: How we rebuilt Next.js with AI in one week

#135
post #10

Nextjs had remote code execution vulnerabilities because of how they implemented react server side. I am not touching an AI version without waiting for a while.

That was a React vulnerability, not a Next one.

It was a vulnerability that only could exist due to the incestuous relationship between React and Vercel. It was something Vercel has been trying to heavily push into React for years (which is why they hired previous react core team members).

Re: How we rebuilt Next.js with AI in one week

#138

Earlier quoted context omitted.

What is it you love about Next that isn’t tied to Vercel and isn’t available elsewhere? I love Next too but I find the value is inextricably linked to Vercel. I can’t imagine choosing to use Next if I’m not choosing it for Vercel’s fancy stuff.

React server components are dope. Server actions are dangerous but powerful. No one has a more mature implementation of either of these than Next.

Of course no one has a more mature implementation of it than Next. The Next.js team designed it themselves!

Re: How we rebuilt Next.js with AI in one week

#139
post #84

I get the gist here but I hate the tone of these sorts of posts. Imagine being a NextJS developer, pouring your heart and soul into it day after day, knowing the codebase inside and out, and seeing some dude on the Cloudflare blog bragging about how he rewrote your project in a week using AI. It's tone deaf. It's not impressive. The tool is hella useful. The messaging is ignorant. This should have been a "we built a…

Tone deaf? It's the reality. Developers shouldn't bury their head under the sand. Chart your course accordingly.

> Rewrote your project

That project would die without user's adoption. Be appreciative. Nextjs is an open source project. What is it with HN that constantly praise the virtue of open source software, but downplay that fact the moment they don't like the outcome?

Re: How we rebuilt Next.js with AI in one week

#140
post #122

[dead]

Warning: Another bot account. This one's a bit more clever in that it's not entirely new -- it's from 2016. Here's some examples from 6 days ago: https://news.ycombinator.com/threads?id=fdefitte&next=470679... Comment 1: 2026-02-18T23:45:12 1771458312 https://news.ycombinator.com/item?id=47067991 Comment 2: 2026-02-18T23:45:32 1771458332 https://news.ycombinator.com/item?id=47067994 20 seconds between its comments. -…

Sure, and we've banned the account, but please email us rather than posting comments like this. hn@ycombinator.com.
Post reply on HN