Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How we rebuilt Next.js with AI in one week

blog.cloudflare.com

Post reply on HN
Print view View original

241–250 of 252 posts

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

#241

Post by barrel_maker »

Would LOVE a more in depth article about the discussions with Claude and how you created the agents to accomplish this! Would be very interested to know what you found the agents were really good at and what they could improve on.

I especially am interested in the initial discussions with Claude about scope, process, and general gameplan. I find that this initial discussion requires a lot of shaping and a lot of input, would love to see more insights into that process from your end!

Awesome stuff

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

#242

Post by cadamsdotcom »

This traffic guided on-demand build thing, can it be powered by a file which has a standard format?

That’d make it vendor-independent - any vendor could create tooling to generate the traffic file, and you could opt to fetch it at build time or check it into your repo.

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

#243

Post by cpursley »

cpursley wrote: post #14
aggregator-ios wrote: post #8

[flagged]

Or just skip/migrate off of the Next.js and other JS SSR rats nets to Elixir and Phoenix LiveView - Claude and Codex are both very good with Elixir now: https://elixirisallyouneed.dev

https://x.com/mrpopov_com/status/2026948153107247426

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

#244

Post by atrocious »

judahmeek wrote: post #207
atrocious wrote: post #185

Earlier quoted context omitted.

Established corporations will be doing yoinking, with a pre-existing credibility. There's a huge incentive to offer these copied services for cents on the dollar, as a way to kill the competition.

Credibility doesn't transfer easily. Anyone who yoinks an open-source package still has to present an argument about why their offering is better than the original maintainer's.

I agree, but it's historically been as simple as "you already use AWS for everything else". For example, ElasticSearch.

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

#245

Post by balder1991 »

twohaibei wrote: post #176
vivzkestrel wrote: post #161

- since you guys are experimenting that much, i have a favor to ask - could you rewrite next and react actually without using a virtual dom at all and use a compiler like svelte instead?

Solid.js might be interesting to you.

There’s even a framework already: https://start.solidjs.com/

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

#246

Post by DoesntMatter22 »

neya wrote: post #237
DoesntMatter22 wrote: post #200

Earlier quoted context omitted.

Elixir is nice but the console feels like the Stone Age by comparison. That drives me a little crazy

I have the opposite opinion - give me stone age over the colored christmas lights anyday :)

It's terribly painful to go and have to import everything you want to use when you want to use the Elixir console. That alone makes it not worth it to me.

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

#247

Post by solarkraft »

pu_pe wrote: post #181

I remember multiple people at HN saying "show me ONE example where AI was used to produce commercial-grade software" like a month ago. Cloudflare alone has posted a couple of examples recently, and yesterday Ladybird was ported to Rust using AI. The most interesting aspect I see in all these examples is that extensive test suites make the work very straightforward. Maybe AI will produce a comeback of test-driven deve…

Claudflare has mainly posted vibeslop with accompanying blog posts making wrong basic statements about the project.

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

#248

Post by xelah »

I don't want to argue if this is good/OK/useful, etc. I'm just wondering where this will go? Assuming it becomes so easy to copycat everything you found online, what would be the motive for anyone to do OSS? If it's trivial to copy, no one will ever care about maintaining any of that. They will just keep it private to themselves or the company they work for.

And the long-term consequence: we will all have to learn to build all of that ourselves. Yes, with the help of AI, but now the entire idea and architecture must be internal because there is nothing you can copy from.

I agree this might be helpful to an extent. We don't need another leftpad or isodd library. There are lots of things we should keep internal and do ourselves. And with AI, it becomes trivial. But if people try to play the whole OSS to their advantage, I think this can end up badly for everyone.

This boils down to one thing: If this is the future of OSS, give me one good reason for anyone to do anything open-source (or even source-open). And then show me from what those models will learn... The old stuff plus what you have internally? Have fun with that.

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

#249

Post by headius »

TheFlyingFish wrote: post #145
slopinthebag wrote: post #57

This is probably the most interesting AI experiment I've seen yet. Looking through the codebase has me wondering where all the code is. I don't know if anyone has had the displeasure of going through the next.js codebase, but I estimate it's at least two orders of magnitude more code than this reimplementation. Which makes me wonder, does it actually handle the edge cases or does it just pass the tests. Like compare…

I imagine offloading a lot of the heavy lifting to Vite helps cut down on the code size.

This. Whole thing struck me as basically an advertisement for Vite. 99% of the base functionality is probably already there, written by humans.

"Use our proprietary SaaS and you too can approximate Next.js in 1/100 as much code using a bit of chicken wire and an LLM".

Whole thing sounded too good to be true, and it was.

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

#250

Post by quantiq »

general_reveal wrote: post #78
slopinthebag wrote: post #57

This is probably the most interesting AI experiment I've seen yet. Looking through the codebase has me wondering where all the code is. I don't know if anyone has had the displeasure of going through the next.js codebase, but I estimate it's at least two orders of magnitude more code than this reimplementation. Which makes me wonder, does it actually handle the edge cases or does it just pass the tests. Like compare…

It is the most passive aggressive thing I’ve ever seen. Cloudflare team had issues with the Next team? And they responded with ‘we can do your whole product with an intern and AI’, lol. Woah.

Yeah, I'm not even sure what this is, or whether or not this is even intended to be a serious project. It just comes across to me as deeply unprofessional. I say this as someone who doesn't even like Vercel and has their own gripes with that bizarrely run company.

The docs say that none of the code has been reviewed or tested properly, so how serious is this for people to run in a production setup where many companies are going are not going to be super enthused that their production environment has been 'vibecoded' in a week? It just reads to me like a not-so-subtle middle finger to the Vercel guys.

On a side note, I find it extremely weird that the current AI era of software development is turning the state of the entire field into a reenactment of Lord of the Flies. Bizarre behavior all around from people who should know better.

Post reply on HN