How we rebuilt Next.js with AI in one week
151–160 of 252 posts
Re: How we rebuilt Next.js with AI in one week
#152Human in the loop, acting as an orchestrator.
Re: How we rebuilt Next.js with AI in one week
#153[dead]
Warning: Another bot account. This one's a bit more clever in that it's not entirely new -- it's from 2016. Here's some examples from 6 days ago: https://news.ycombinator.com/threads?id=fdefitte&next=470679... Comment 1: 2026-02-18T23:45:12 1771458312 https://news.ycombinator.com/item?id=47067991 Comment 2: 2026-02-18T23:45:32 1771458332 https://news.ycombinator.com/item?id=47067994 20 seconds between its comments. -…
Re: How we rebuilt Next.js with AI in one week
#154> 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…
Re: How we rebuilt Next.js with AI in one week
#155I actually was thinking on creating something similar. Congrats to the Cloudflare team
Re: How we rebuilt Next.js with AI in one week
#156[flagged]
Wait a minute, can we at least wait until this dethrones next.js before making suck claims?
Re: How we rebuilt Next.js with AI in one week
#157Earlier quoted context omitted.
> There's no way Cloudflare could have pulled this off without next's very own tests. I'm very uncovinced. History showed us very complex systems reverse engineered without access to the source code. With access to the source code, coupled with the rapid iteration of AI, I don't see any real moat here; at best a slight delay.
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…
Re: How we rebuilt Next.js with AI in one week
#158Earlier quoted context omitted.
What is it you love about Next that isn’t tied to Vercel and isn’t available elsewhere? I love Next too but I find the value is inextricably linked to Vercel. I can’t imagine choosing to use Next if I’m not choosing it for Vercel’s fancy stuff.
React server components are dope. Server actions are dangerous but powerful. No one has a more mature implementation of either of these than Next.
Re: How we rebuilt Next.js with AI in one week
#159I 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…
asdf was the hot shit for quite a while, with people (myself included) invoking all kinds of shell arcanum to make it faster - then mise (née rtx) came out, and it was game over. Compatible with asdf’s ecosystem, but infinitely faster.
Poetry was incredibly popular, along with various other competitors, and then uv came out.
I get what you’re saying about the AI angle, because it’s somewhat different when a human takes your crown by dint of pure skill, but it’s gotta sting either way.
Re: How we rebuilt Next.js with AI in one week
#160The 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?