Summary Digital Access & Developer Empowerment Advocates
This technical blog post announces vinext, an open-source Next.js alternative built on Vite with significant performance improvements. The content advocates for democratized access to advanced development tooling through cost-effective AI assistance, free and open-source distribution, and transparent technical disclosure. While the primary focus is technical rather than explicitly human-rights oriented, the post demonstrates consistent support for developer agency, information access, and community participation in technological advancement.
This is pretty fascinating and comes with some complicated AI-world incentives that I've been ruminating on lately. The better you document your work, the stronger contracts you define, the easier it is for someone to clone your work. I wouldn't be surprised if we end up seeing open source commercial work bend towards the SQLite model (open core, private tests). There's no way Cloudflare could have pulled this off without next's very own tests.
Speaking more about the framework itself, the only real conclusion I have here is that I feel server components are a misunderstood and under-utilized pattern and anyone attempting to simplify their DX is a win in my book.
Next is very complex, largely because it has incrementally grown and kept somewhat backwards compatible. A framework that starts from the current API surface and grows can be more malleable and make some tough decisions here at the outset.
Crazy to see it's already being run on a .gov domain[0]. TTFGOV as a new adoption metric?
someone 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.
Nextjs had remote code execution vulnerabilities because of how they implemented react server side. I am not touching an AI version without waiting for a while.
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. Meanwhile Vite is a better core layer than the garbage the Next people use, but you still get the full Next functionality.
I wish Cloudflare the best of luck with this fork: I hope it succeeds and gets proven so I can use it at my company!
i love how this disintermediates the next.js/vercel axis, which seems to be determined to make basically everything hard except for exactly what they want to do. as much as i love what vercel has done for open source in general (amazing stuff!) it is hard to interpret some of the stuff they do with next as anything other than vendor lock-in bs… the kind that i know is not in their hearts.
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, at the organisational level, it still makes sense to hire the “vision” behind the framework, rather than just clone it. Alternatively, maybe AI has improved that much in 1 month!
> Most abstractions in software exist because humans need help. We couldn't hold the whole system in our heads, so we built layers to manage the complexity for us.
Kind of a sloppy statement, but I don't think it's accurate to say abstraction or layering exists in software just because humans need help comprehending it. Abstractions often exist to capture the essence of some aspect of the real world, and to allow for software reuse. AIs will still find reusing software useful? Secondly, you equate "abstractions" with "layers" which aren't really the same thing. Layers are more about separation of concerns. Maybe it could be argued layering is a type of abstraction.
This 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 the two form implementations for example. Vinext is a completely different implementation compared to what the Next.js version does. Is their behaviour actually the same? The rewrite looks incredibly naive.
The 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 actually a good framework? Who knows.
I'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, I don't believe people "rebuilt X product in a week".
fwiw, I just tried running the agent-skill they provide for fun to migrate an app-router based next 15 site and the end result is it entirely failed to start.
Vite just hangs when running vinext dev, with no output in logs whatsoever beyond printing`vinext dev (Vite 7.3.1)`.
I wonder to what extent you should say you "rebuilt" something when the most basic hello world example doesn't work. And I wonder to what extent it makes sense to call it "from scratch" if you inherit a battle tested extensive test suite from the thing you're rebuilding, and the thing you're rebuilding is part of the training data.
Here's the first paragraph of Harry Potter and the philosopher's stone. I rewrote it from scratch, apparently:
Mr. and Mrs. Dursley, of number four, Privet Drive, were proud to say that they were perfectly normal, thank you very much. They were the last people you’d expect to be involved in anything strange or mysterious, because they just didn’t hold with such nonsense. Mr. Dursley was the director of a firm called Grunnings, which made drills. He was a big, beefy man with hardly any neck, although he did have a very large mustache.
> 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 claude already has next's entire source code in it's training data?
The buried lede here is the Astro acquisition timing. Cloudflare bought Astro a month ago, and now they're showing they can replicate Next.js's API surface with AI in a week. The strategic play isn't vinext itself — it's signaling to the market that framework lock-in is dissolving.
If you're a Next.js shop stuck on Vercel because self-hosting is painful, Cloudflare just gave you two exit ramps: Astro (for new projects) and vinext (for existing ones). Whether vinext is production-ready today matters less than what it represents for Vercel's pricing power.
The real question nobody's asking: if your framework's value can be replicated by targeting its test suite, what exactly are you paying for with Vercel's premium tiers? The answer used to be "the only place Next.js runs well." That moat is eroding fast.
I remember multiple people at HN saying "show me ONE example where AI was used to produce commercial-grade software" like a month ago. Cloudflare alone has posted a couple of examples recently, and yesterday Ladybird was ported to Rust using AI.
The most interesting aspect I see in all these examples is that extensive test suites make the work very straightforward. Maybe AI will produce a comeback of test-driven development.
It's going to get increasingly difficult to sell software when there is no moat to replication. We're quickly reaching the point where you can just tell an agent "learn what this software does and then code it".
> The better you document your work, the stronger contracts you define, the easier it is for someone to clone your work.
Well said; this is my thinking as well. One person or organization can do the hard work of testing multiple approaches to the API, establishing and revising best practices, and developing an ecosystem. Then once things are fairly stable and well-understood, another person can just yoink it.
I have little empathy for Vercel, and here they're kind of being hoist by their own petard of inducing frustration in people who don't use their hosting; but I'm concerned about how smaller-scale projects (including copyleft ones) will be laundered and extinguished.
> 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.
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.
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.
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.
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
Thank you. This is the part that shocks me the most. I was always wary of Next.js for this exact reason (in fact, I refused to use it for personal projects before the RCE because I was scared that I would make a mistake and leak server-side data to the client.
Bugs like this are easy to happen and even easier to miss if you’re generating thousands of lines of code with AI.
Astro isn’t solving the same surface as next. Astro is great for static sites with some dynamic behavior. The same could be said about next depending on how you write your code, but next can also be used for highly dynamic websites. Using Astro for highly dynamic websites is like jamming a square peg into a round hole.
We use Astro for our internal dev documentation/design system and it’s awesome for that.
It is the most passive aggressive thing I’ve ever seen. Cloudflare team had issues with the Next team? And they responded with ‘we can do your whole product with an intern and AI’, lol.
I don't necessarily buy it either, but TFA talks about the test suite. They basically pulled 2k unit tests and 400 E2E tests from Next and made sure they all passed.
Weird, I hate Next and I love Vite. We have a big (I mean _really_ big) production app that runs on Next.js at work and it's the slowest thing I've ever worked on. I had to upgrade my machine to an M4 Pro just to get local dev compile times down from 5-8 minutes to ~30-60 seconds per route. And my hot refreshes are down from ~15-20 seconds to 5-10. It's _bad_. All the Next.js team does is give you the run-around and link to their docs and say here, try these steps, you're probably doing something wrong, etc. Nope. The framework is just slow. They use simple toy apps to demo how fast it is, but nobody tells you how slow it is at scale.
> I wouldn't be surprised if we end up seeing open source commercial work bend towards the SQLite model (open core, private tests).
Wouldn't this just mean that actual open source is the tests? or spec? or ... The artifact which acts as seed for the program, what ever that ends up being?
>The only people that have trouble with this development are the gatekeepers who think that code should be sacred and revered by itself. That is a perversion of computing, and we got the wrong group of people there.
I'm not sure who the hell you're talking about, but I'd guess from your comment that you have a pretty high opinion of yourself.
> 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.
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 for why it's so much smaller, by building on top of Vite and their react + rsc plugins there is a whole lot of code that we don't need to write. That's where a significant portion of the LOC difference comes from.
The post advocates for open access to software development knowledge and tools. It frames transparency in the development process (showing benchmarks, linking open-source code) as enabling free expression and information sharing among developers.
FW Ratio: 60%
Observable Facts
Article provides direct links to GitHub repository where source code is publicly accessible.
Benchmarks and technical comparisons are transparently disclosed with methodology noted.
Content is published on public blog without access restrictions or registration requirements.
Inferences
Free access to blog post and GitHub repository supports freedom of expression and information sharing principles.
Transparent disclosure of benchmarks and methodologies demonstrates commitment to open knowledge sharing.
The post describes a development approach that empowers individual developers and facilitates developer communities. The narrative suggests that lower barriers to advanced tooling support collective developer agency and association.
FW Ratio: 60%
Observable Facts
The vinext project is open-source on GitHub, enabling community contributions and collective development.
Post mentions 'customers running it in production,' suggesting a community of practice around the tool.
Vite is described as 'used by most of the front-end ecosystem,' emphasizing community adoption.
Inferences
Open-source and community-driven development model supports collective freedom of association among developers.
The emphasis on broad ecosystem adoption suggests support for developer communities to collectively adopt new tooling.
The post describes how technological advancement (4x faster builds, 57% smaller bundles) improves developer productivity and access to benefits of scientific and technical progress. The focus on cost-effective AI-assisted development ($1,100 in tokens) democratizes access to advanced tooling.
FW Ratio: 60%
Observable Facts
Post explicitly emphasizes performance improvements (4x faster builds, 57% smaller bundles) that benefit developers.
The $1,100 cost for AI-assisted rebuilding is highlighted as economically accessible compared to traditional development.
Open-source availability enables developers worldwide to benefit from technical advancement without licensing costs.
Inferences
Performance improvements and cost efficiency frame technological progress as broadly accessible to developers.
Open-source model ensures participation in scientific/technical progress is not restricted by proprietary licensing.
Content advocates for technological accessibility and democratization of software development. The post frames AI-assisted development as enabling broader access to advanced tooling, supporting the Preamble's vision of universal human dignity and freedom through technology.
FW Ratio: 60%
Observable Facts
The article announces an open-source project (vinext) freely available for download and use.
The post explicitly states the project is deployed to GitHub and accessible to developers without cost.
Content emphasizes that existing Next.js code can be used with minimal changes, reducing barriers to adoption.
Inferences
The narrative frames technological progress as democratizing access to powerful development tools, aligning with Preamble principles of universal dignity.
The emphasis on cost-effectiveness ($1,100 in tokens) suggests advocacy for reducing barriers to technological innovation.
The article's framing of AI-assisted development as enabling broader participation in software creation suggests an inclusive approach to technological agency and opportunity. However, the primary focus is technical, not explicitly human-rights oriented.
FW Ratio: 67%
Observable Facts
The post describes how one engineer used AI to rebuild a framework, making advanced development accessible to a broader audience.
The project is open-source and available on GitHub with no enrollment restrictions.
Inferences
By demonstrating AI-assisted development outcomes, the content suggests equal opportunity for technological participation regardless of resources.
The post describes developer-centric features without explicit discrimination concerns. The focus on interoperability and cross-platform compatibility implies accessibility to diverse developer groups.
FW Ratio: 60%
Observable Facts
Page source contains semantic HTML heading elements with IDs for navigation.
CSS includes @media(prefers-reduced-motion) media query that disables animations for accessibility.
Content describes multi-platform deployment without restrictions based on developer type.
Inferences
The accessible HTML structure and motion-preference support suggest structural commitment to non-discriminatory access.
Platform-agnostic deployment aligns with anti-discrimination principles by not favoring certain developer environments.
Content does not address privacy concerns. Post focuses entirely on technical benefits without discussing data collection or privacy implications of the tooling.
FW Ratio: 60%
Observable Facts
Page source contains OneTrust consent wrapper and Zaraz tag manager initialization code.
Consent mechanism loads Zaraz analytics only if user has accepted 'C0004' consent category.
Script includes listener for 'consent.onetrust' events, indicating consent-driven tracking.
Inferences
The presence of Zaraz and OneTrust indicates third-party data collection infrastructure that may limit privacy expectations despite consent mechanisms.
Consent-dependent tracking suggests awareness of privacy rights but does not eliminate privacy-related concerns.
Semantic HTML and accessible design support universal access to content about technological development. Open-source project enables participation in technical advancement.
Page source reveals OneTrust consent management and Zaraz tag manager active. Analytics tracking is consent-dependent but enabled by default unless explicitly opted out.
Content advocates for technological accessibility and democratization of software development. The post frames AI-assisted development as enabling broader access to advanced tooling, supporting the Preamble's vision of universal human dignity and freedom through technology.
The article's framing of AI-assisted development as enabling broader participation in software creation suggests an inclusive approach to technological agency and opportunity. However, the primary focus is technical, not explicitly human-rights oriented.
Claims of '4x faster' and '57% smaller bundles' compared to Next.js, with benchmarks shown but caveats about methodology appear only in body text after headline claims.
appeal to authority
Invocation of Cloudflare's resources and multiple customer validation ('already have customers running it in production') to establish credibility.
build 1ad9551+j7zs · deployed 2026-03-02 09:09 UTC · evaluated 2026-03-02 10:41:39 UTC
Support HN HRCB
Each evaluation uses real API credits. HN HRCB runs on donations — no ads, no paywalls.
If you find it useful, please consider helping keep it running.