How we rebuilt Next.js with AI in one week

Re:How we rebuilt Next.js with AI in one week by vlucas on Tuesday February 24, 2026 @07:39PM (#47145728)

The basic premise of Next is good, but it definitely has more overhead that in should, has odd "middleware", and is very hard to optimize. I view this mostly as a React problem though since any page requires full hydration and ships everything to the client. RSCs are... not my favorite for sure.

I too have been very frustrated by this, and I made an "Astro for dynamic sites" TypeScript framework called Hyperspan ( https://www.hyperspan.dev ) that aims to fill the gap in the JS ecosystem for a modern fully dynamic option that, similar to Astro, makes dynamic islands easy. I have enjoyed using it in all my own projects. Check it out if you want.

[ Parent | on HN ]

Re:How we rebuilt Next.js with AI in one week by switz on Tuesday February 24, 2026 @07:49PM (#47145807)

RSC by design does not ship everything to the client. That's one of its basic premises. It ships markup, composed in client interactivity, but you can shed a lot of the code required curate that markup.

[ Parent | on HN ]

Re:How we rebuilt Next.js with AI in one week by vlucas on Wednesday February 25, 2026 @11:54AM (#47154138)

I obviously meant traditional React components, not RSC. RSC can eliminate some client code, but they can be very awkward to use in practice, and lines between server and client get blurry really fast. The mental model is difficult for many to fully grok. I say this as someone who has lead engineering teams with folks of varying skill levels. RSCs are not worth the extra complexity and mental overhead they bring.

[ Parent | on HN ]