181–190 of 252 posts
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.
Earlier quoted context omitted.
React server components are dope. Server actions are dangerous but powerful. No one has a more mature implementation of either of these than Next.
It is hilarious to me that the industry has reinvented serving HTML to clients, but with many intermediate steps, and this is heralded as groundbreaking.
God cloudflare's blog quality has fallen off a fuckin cliff ehh. Used to be so good now its just llm slop both content and actual writing.
Gotta hand it to 'em though - posting this less than a month after the Matrix boondoggle certainly is, uh, audacious.
Also looking forward to Vercel's version of https://matrix.org/blog/2026/01/28/matrix-on-cloudflare-work....
Earlier quoted context omitted.
> 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…
> 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…
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 deve…
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…
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…
Now, you will not develop it further, it will face the same fate as OpenNext and adaptors.
Here's what is buried a bit in the text: --- start quote --- Something like 95% of vinext is pure Vite. The routing, the module shims, the SSR pipeline, the RSC integration: none of it is Cloudflare-specific. --- end quote --- The real achievement is human-built Vite (and it is an amazing project). Since Next.js's API surface and capabilities are known, this is actually quite a good use of AI: re-implement some funct…