React Meta-Framework Feels Broken, Here's Why

I'm the author of this article, and this is the second time I've built a framework. I co-created RedwoodJS with Tom Preston-Werner several years ago - and we came up with some novel ideas, but I had a nagging feeling that something wasn't right.

A failed-startup and a kid later... and I'm back. I couldn't let go of the original vision of RedwoodJS, but I wanted to start from scratch. So we built RedwoodSDK, which is a React framework for Cloudflare. It starts as a Vite Plugin that gives you server-side-rendering, RSC, streaming, and realtime capabilities.

Our standards based route feels invisible, with simple pattern matching, middleware and interrupters. You receive a request and return a response. You own every byte over the wire.

There's zero magic. Just TypeScript, modules, functions, values, and types.

A new blog post argues that today’s React meta-frameworks like Next.js and Remix are too abstract and “feel broken,” adding complexity through magic and indirection. It introduces RedwoodSDK as a simpler, more transparent alternative that prioritizes native web APIs and production-parity development.

Aren't the "defineApp" and "route" methods in rwsdk also magic? It feels like rwsdk is just being more deliberate about when and where to introduce those magic functions.

I'm a big fan of rwsdk so far. Thanks for building!

    export default {
        fetch({ request }) {
          return new Response('ok')
        } 
    }