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

121–130 of 252 posts

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

#121

Post by tengbretson »

3rodents wrote: post #27
hungryhobbit wrote: post #16

Man, I love Next ... but I also love Vite ... and I hate the Next team, because they focus on fancy new features for 0.1% of their users, at the complete expense of the other 99.9% of the Next community (who they basically ignore). This gives someone like me everything we want. Better performance is something the Next community has been begging for for years: the Next team ignored them, but not the Cloudflare team. M…

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.

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

#122

Post by rob »

fdefitte wrote: post #114

[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.

--

or another example:

Comment 1: 2026-02-18T20:06:49 1771445209 https://news.ycombinator.com/item?id=47065649

Comment 2: 2026-02-18T20:07:12 1771445232 https://news.ycombinator.com/item?id=47065653

23 seconds between its comments.

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

#123

Post by igravious »

JustSkyfall wrote: post #83
qudat wrote: 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.

Rails 8 is surprisingly good nowadays. It absolutely still has its share of problems (e.g. Bundler being slow, the frontend story being crappy without Inertia, lack of types which is a biggie, memory) but it is still a fantastic framework imo.

Somebody should port uv to Ruby :/

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

#124

Post by hinkley »

thousand_nights wrote: post #33
hungryhobbit wrote: post #16

Man, I love Next ... but I also love Vite ... and I hate the Next team, because they focus on fancy new features for 0.1% of their users, at the complete expense of the other 99.9% of the Next community (who they basically ignore). This gives someone like me everything we want. Better performance is something the Next community has been begging for for years: the Next team ignored them, but not the Cloudflare team. M…

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

Sounds like Tapestry. Had a friend who loved it but he stopped talking about it after the 4th major architecture shift.

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

#125

Post by csomar »

I have done a similar thing with my web app (codeinput.com) and honestly wouldn’t touch this thing for even a fun project. My reason to migrate was two fold: nextjs simply didn’t work with Cloudflare workers and IBM carbon required ‘use client’ for every page which meant that no HTML was generated. Everything was client side.

Google Gemini, at the time, created an SSG solution which I had spent the next 3-4 months fixing bugs for. Consequently, I had to understand the whole SSG build step and all the wrong design decisions the AI made that resulted in the site getting a horrible core web vitals score. In the end, I just put the site behind a white “div” that disappear when the page finally loads. SSR is way more complex than it sounds.

This project (along with the quantum post) is quite concerning. It’s not clear why Cloudflare has decided to take this direction. If you want to know why LLMs are completely unable to produce something even close to NextJS, a better solution would have been to ask the LLM to fix the opennext adapter rather than building a new framework from scratch.

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

#126

Post by kopirgan »

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…

What do you use?!

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

#128

Post by neya »

qudat wrote: post #45
hungryhobbit wrote: post #16

Man, I love Next ... but I also love Vite ... and I hate the Next team, because they focus on fancy new features for 0.1% of their users, at the complete expense of the other 99.9% of the Next community (who they basically ignore). This gives someone like me everything we want. Better performance is something the Next community has been begging for for years: the Next team ignored them, but not the Cloudflare team. M…

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.

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

#129

Post by adithyassekhar »

> We also want to acknowledge the Next.js team. They've spent years building a framework that raised the bar for what React development could look like. The fact that their API surface is so well-documented and their test suite so comprehensive is a big part of what made this project possible.

Hi next.js devs, we like to acknowledge the effort you put for writing good tests so we were able to rip it off. You know claude already has next's entire source code in it's training data?

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

#130

Post by cheshire_cat »

igravious wrote: post #123
JustSkyfall wrote: post #83

Earlier quoted context omitted.

Rails 8 is surprisingly good nowadays. It absolutely still has its share of problems (e.g. Bundler being slow, the frontend story being crappy without Inertia, lack of types which is a biggie, memory) but it is still a fantastic framework imo.

Somebody should port uv to Ruby :/

It's called rv: https://github.com/spinel-coop/rv
Post reply on HN