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

31–40 of 252 posts

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

#31

Post by bastardoperator »

ratorx wrote: 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…

I think they just want steer users/developers to CF products, maybe not? It is interesting to see the two platforms. I've moved to svelte, never been a frontend person either but kind of enjoying it actually.

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

#32

Post by 3rodents »

ratorx wrote: 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 websites from Vercel to Cloudflare. Realistically, anyone moving their next.js site to Cloudflare is going to end up migrating to Astro eventually.

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

#33

Post by thousand_nights »

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

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

#34

Post by [deleted] »

ratorx wrote: 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…

[deleted]

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

#35

Post by bbkane »

acedTrex wrote: post #13

God cloudflare's blog quality has fallen off a fuckin cliff ehh. Used to be so good now its just llm slop both content and actual writing.

This is interesting to my on both a technical level as well as a social-political level. I wonder what impact "AI-washing" will have on licensing for example

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

#37

Post by satvikpendem »

ratorx wrote: 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…

> which from my definitely-not-a-frontend-person perspective seems to tackle a similar problem to Next.

It does not. Astro is more for static sites not dynamic web apps.

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

#39

Post by himata4113 »

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…

I mean you don't want really want to use javascript for the backend anyway... What's the problem with just using vite and any backend of your choosing?
Post reply on HN