Live data from Hacker News

How we rebuilt Next.js with AI in one week

blog.cloudflare.com

51–60 of 252 posts

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

#51

someone spent over 1000 dollars to replicate the functionality of Next.JS, even 1 dollar would seem too much somehow. I suppose that is me being overly retributive.

> it builds production apps up to 4x faster and produces client bundles up to 57% smaller.

I suppose that is you being overly retributive indeed.

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

#52

[flagged]

> Code never was and never should have been the product in and of itself

Except that the code completely and precisely defines the actual product. Bad code => bad product.

> code should be sacred and revered by itself

As a production of the hand and mind, code should be revered - if only as the mark of the human or groups of humans that made it.

> the wrong group of people

The group of people who care deeply about the world around them.

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

#53
post #25

I find it interesting that they bought Astro ( https://blog.cloudflare.com/astro-joins-cloudflare/ ), which from my definitely-not-a-frontend-person perspective seems to tackle a similar problem to Next. A month ago. If it is so cheap to make something that they recommend using (rather than a proof of concept), why buy Astro (presumably it was more expensive than the token cost of this clone?). One conclusion is that…

Astro is a different paradigm. Acquiring Astro gives Cloudflare influence over a very valuable class of website, in the same way Vercel has over a different class from their ownership of Next.js. Astro is a much better fit for Cloudflare. Next.js is very popular and god awful to run outside of Vercel, Cloudflare aren’t creating a better next.js, they’re just trying to make it so their customers can move Next.js websi…

Can you talk more about this? What’s wrong with cloudflare pages plus Nextjs? Why do you need Astro?

Thanks

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

#54
post #25

I find it interesting that they bought Astro ( https://blog.cloudflare.com/astro-joins-cloudflare/ ), which from my definitely-not-a-frontend-person perspective seems to tackle a similar problem to Next. A month ago. If it is so cheap to make something that they recommend using (rather than a proof of concept), why buy Astro (presumably it was more expensive than the token cost of this clone?). One conclusion is that…

Astro has "server islands" which rely on a backend server running somewhere. If 90% of the page is static but you need some interactivity for the remaining 10%, then Astro is a good fit, as that's what makes it different than other purely static site generators. Unlike Next.js, it's also not tied to React but framework-agnostic.

Anyways, that's why it's a good fit for Cloudflare: that backend needs to be run somewhere and Astro is big enough to have some sort of a userbase behind them that Cloudflare can advertise its service to. Think of it more as a targeted ad than a real acquisition because they're super interested in the technology behind it. If that were the case, they could've just forked it instead of acquiring it.

From Astro's perspective, they're (presumably) getting more money than they ever did working on a completely open source tool with zero paywalls, so it's a win-win for both sides that Cloudflare couldn't get from their vibe-coded project nobody's using at the moment.

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

#56
> Most abstractions in software exist because humans need help. We couldn't hold the whole system in our heads, so we built layers to manage the complexity for us.

Kind of a sloppy statement, but I don't think it's accurate to say abstraction or layering exists in software just because humans need help comprehending it. Abstractions often exist to capture the essence of some aspect of the real world, and to allow for software reuse. AIs will still find reusing software useful? Secondly, you equate "abstractions" with "layers" which aren't really the same thing. Layers are more about separation of concerns. Maybe it could be argued layering is a type of abstraction.

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

#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 the two form implementations for example. Vinext is a completely different implementation compared to what the Next.js version does. Is their behaviour actually the same? The rewrite looks incredibly naive.

https://github.com/vercel/next.js/blob/b8cbaad24ca66ec673a7b...

https://github.com/cloudflare/vinext/blob/main/packages/vine...

Either way, pretty impressive.

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

#58
post #4

This is pretty fascinating and comes with some complicated AI-world incentives that I've been ruminating on lately. The better you document your work, the stronger contracts you define, the easier it is for someone to clone your work. I wouldn't be surprised if we end up seeing open source commercial work bend towards the SQLite model (open core, private tests). There's no way Cloudflare could have pulled this off wi…

[dead]

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

#59
The article say that "Next.js is well-specified." I... don't think this is actually true. It certainly has lots of documentation, but as has come up time and time again, there are tons of undocumented or poorly documented behaviors that have been the cause of consternation.

So I kinda wonder, did they just create the framework that Next.js claims to be but never has been? And is Next.js without the hidden stuff actually a good framework? Who knows.

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

#60
post #25

I find it interesting that they bought Astro ( https://blog.cloudflare.com/astro-joins-cloudflare/ ), which from my definitely-not-a-frontend-person perspective seems to tackle a similar problem to Next. A month ago. If it is so cheap to make something that they recommend using (rather than a proof of concept), why buy Astro (presumably it was more expensive than the token cost of this clone?). One conclusion is that…

Astro isn’t solving the same surface as next. Astro is great for static sites with some dynamic behavior. The same could be said about next depending on how you write your code, but next can also be used for highly dynamic websites. Using Astro for highly dynamic websites is like jamming a square peg into a round hole.

We use Astro for our internal dev documentation/design system and it’s awesome for that.

Post reply on HN