[dead]
gtfo clanker
How we rebuilt Next.js with AI in one week
221–230 of 252 posts
Re: How we rebuilt Next.js with AI in one week
#222for most folks -- just user Inertia + Django | Rails
Re: How we rebuilt Next.js with AI in one week
#223Man, 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…
You think you'll get better long-term support from an experiment that a single engineer did in his spare time?
what if we all move to vinext? I'm asking claude to migrate us in a git worktree using a team of agent, installed the vinext skill to help with that, it did it in 10min
also why do you need support? agents are the support
Re: How we rebuilt Next.js with AI in one week
#224This 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…
I ported the number theory parts of sagemath in typescript, I thought that was pretty interesting as well xD https://github.com/zksecurity/sagemath-ts
Re: How we rebuilt Next.js with AI in one week
#225The most obnoxious man in the middle of the Internet rips off other people's code. Who knew? Does anyone have experiences with the EU alternative bunny.net?
I've been using their cloud storage and CDN for a couple of years. No complaints. Super reliable.
Re: How we rebuilt Next.js with AI in one week
#226I'm deeply skeptical of the "X reimplemented and it was super easy" thing. The devil is in the detail. So many edge cases unlikely to be there. So many details or fine details unlikely to be there. Years of bug fixes. If it is literally a drop in replacement and it passes all the tests, and you're replicating something with and extremely thorough test suite, then sure I'll give you the benefit of the doubt. Otherwise…
God speed to the poor souls that have to make it actually work in the long run:
"I can say that with some authority. Yes, I'm the one who wrote most of this project, but I'm also the director in charge of the entire Cloudflare Workers org, almost 80+ people at this point. I'm not just an IC engineer who has to find time to justify continuing to work on this. I can literally put people on it, and I've already been talking to the team about how to do exactly that."
https://github.com/cloudflare/vinext/issues/21#issuecomment-...
Re: How we rebuilt Next.js with AI in one week
#227> 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 cla…
This is basically distillation for JavaScript frameworks. We're not creating new ones fast enough. So we'll just start distilling the ones we have.
Re: How we rebuilt Next.js with AI in one week
#228> 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 cla…
Clownflare engineers are in the chat now doing damage control and downvote opposition. Soon jgrahamc will appear and whitewash the theft.
"I'm also the director in charge of the entire Cloudflare Workers org, almost 80+ people at this point. I'm not just an IC engineer who has to find time to justify continuing to work on this. I can literally put people on it, and I've already been talking to the team about how to do exactly that." -Steve Faulkner
https://github.com/cloudflare/vinext/issues/21#issuecomment-...
Re: How we rebuilt Next.js with AI in one week
#229The 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 actua…
The primary reason I moved away from NextJS is the constant stream of bugs. Never seen any framework or library perform as poorly as it past v0.
Re: How we rebuilt Next.js with AI in one week
#230someone 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.
coulda forked it for free