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

231–240 of 252 posts

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

#231

Post by dadbod »

TonyStr wrote: post #178
ZebulonP wrote: post #147

Earlier quoted context omitted.

(to be transparent - I'm a Cloudflare engineer) The behavior isn't entirely the same and reaching 100% parity is a non-goal, but there are a few things to note. This is still a very early implementation and there are undoubtedly issues with the implementation that weren't covered in next's original test suite (and thus not inherited) while not being obvious enough to pop up with all the apps we've tried so far. As fo…

Why is parity a non-goal? The blog post states: > The result, vinext (pronounced "vee-next"), is a drop-in replacement for Next.js "Drop-in" in my mind means I can swap the next dependency for the vinext dependency and my app will function the same. If the reality is that I have to spend hours or days debugging obscure edge cases that appear in vinext, I wouldn't exactly call that a drop-in replacement. I understand…

Makes me wonder how the hell all the tests passed?!

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

#233

Post by TheAlexLichter »

dmix wrote: post #97

What the status on Vite Rolldown? Is it nearing production?

Vite 8 is in beta, so you can try it out already. See https://voidzero.dev/posts/announcing-vite-8-beta

Rolldown is in RC, meaning no more breaking changes (except for experimental features). See https://voidzero.dev/posts/announcing-rolldown-rc

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

#235

Post by remus »

atrocious wrote: post #185
judahmeek wrote: post #172

Earlier quoted context omitted.

> Then once things are fairly stable and well-understood, another person can just yoink it. That transparency & availability for community contributions or forks is the point of open-source. If you're only using open-source as marketing because you're bad at marketing, then you should probably go closed source & find a non-technical business partner. Whoever "yoinks" the package runs into the same problem because the…

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.

It'll be interesting to see if this happens at a service level too. Like how lots of companies offer an S3 compatible API, will companies start offering similar services and building a compatibility layer over the top as an easy way to for customers to transition? You could use the existing service as a test suite to check your compatibility API behaves the same as the original product.

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

#236

Post by neya »

culopatin wrote: post #198
neya wrote: post #150

Earlier quoted context omitted.

Agreed 100%. I shifted to Phoenix/Elixir years ago but I still love Rails for all the sensible defaults it provides.

How is the elixir job market these days?

You can find specialized roles than Rails and usually more experienced (understandably) but most companies would be really open if you told them you have a Rails background but want to learn Elixir.

The pool size is less, but the pay is more (depending on your demographics, experience, etc) in my personal experience.

But, honestly I chose it not for the market, it's just a better programming language to build stuff, period.

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

#237

Post by neya »

DoesntMatter22 wrote: post #200
neya wrote: post #150

Earlier quoted context omitted.

Agreed 100%. I shifted to Phoenix/Elixir years ago but I still love Rails for all the sensible defaults it provides.

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 :)

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

#238

Post by codenomnom »

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…

This is EXACTLY how I've felt. We've said it out loud multiple times but I think we never did it together.

I just wrote an open letter to fix Next.js. The goal is to compile a list of needs for whoever decides to fix those in any way possible...

https://please-fix-next.com/

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

#239

Post by codenomnom »

tills13 wrote: post #84

I get the gist here but I hate the tone of these sorts of posts. Imagine being a NextJS developer, pouring your heart and soul into it day after day, knowing the codebase inside and out, and seeing some dude on the Cloudflare blog bragging about how he rewrote your project in a week using AI. It's tone deaf. It's not impressive. The tool is hella useful. The messaging is ignorant. This should have been a "we built a…

I partially agree with you, because Vercel put a ton of effort on this one. And the repo (and features list) is massive.

On the other hand, I do believe they drifted too much and stopped listening. As someone else said it - most of the fancy features are used by 1% of the projects, and everything else is buried in hacks and workarounds.

I also agree the tone (and especially the AI brag) is a bit too much. And at the same time it's honest - it doesn't need to be THAT hard and complex. Nor slow :)

That's why I've written an open letter to fix Next.js, to whomever wants to do it (Vercel, Cloudflare or anyone else). Because we have needs, and we cannot play this game anymore...

https://please-fix-next.com/ if you're interested

Post reply on HN