- since you guys are experimenting that much, i have a favor to ask
- could you rewrite next and react actually without using a virtual dom at all and use a compiler like svelte instead?
How we rebuilt Next.js with AI in one week
161–170 of 252 posts
Re: How we rebuilt Next.js with AI in one week
#162I am so over reinventing the wheel in tech, I feel as if that's 99% of where the money and time goes
Re: How we rebuilt Next.js with AI in one week
#163[flagged]
> if your framework's value can be replicated by targeting its test suite,
Side note: this is also why SQLite's full test suite is proprietary / private
Re: How we rebuilt Next.js with AI in one week
#164Earlier quoted context omitted.
> Surprised this didn't get a higher placement on the HN front page, only 34 points? Vercel may be bad, but they have been a net positive to the web landscape, so many projects are alive because of them. And I truly respect the hard work the next devs put into their code and test suites. I'm surprised any self respecting dev even votes this up.
Because it hurts feelings? If someone reproduced the Linux kernel would you feel the same way?
If it is a multi million dollar company? Yes absolutely.
Re: How we rebuilt Next.js with AI in one week
#165> 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.
It's wild. If I need to steal someone's code, I just need to let an ai crawl it and it'll regurgitate the same thing. I can't wait for it to recreate marvel movies.
Re: How we rebuilt Next.js with AI in one week
#166Earlier quoted context omitted.
I have tried to post this here but it has not got traction. I have a demonstrated process here on my blog (all hand written without AI). This bit about how to brute force decompilation: https://reorchestrate.com/posts/your-binary-is-no-longer-saf... And this about how to do the conversion and address the LLM hallucination problem: https://reorchestrate.com/posts/your-binary-is-no-longer-saf... Yes, it is absolutely p…
I am curious, have you attempted to do this to any binary packed with commercial obfuscation/"virtualization" schemes (e.g. Orean's Themida/Code Virtualizer and VMProtect)?
No, I would need to find a binary to test on. I suspect it would produce horrible code at the decompiler layer but ultimately I would expect that function signatures are still relatively clean?
Its scary - once you get the differential testing harness set up it seems to be just a matter of time/tokens for it to stubbornly work through it.
Re: How we rebuilt Next.js with AI in one week
#167[flagged]
Cloudflare also backs https://opennext.js.org/
Re: How we rebuilt Next.js with AI in one week
#168Re: How we rebuilt Next.js with AI in one week
#169[flagged]
as much as people hate nextjs, no one is going to migrate their production app to a "one week old project"
Even cloudfare mentions that this is still in experimental phase.
In future, it may become something worthwhile. maybe enough for vercel to kill turbopack for good.
Re: How we rebuilt Next.js with AI in one week
#170Earlier quoted context omitted.
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
Is there any reason to keep upgrading if the apps keep doing their jobs perfectly fine? Pull in a stable version of the framework and the associated docs and stay there.
For example: https://nextjs.org/blog/CVE-2025-66478