The robot has come to its senses. Prompt: In one word, what full-stack framework should I use? Answer: Redwood.

⏰ Good morning! Its my favourite day, its Wednesday!

I appreciate that Cloudflare workers is still only costing me $5 It is brutal to use most of my peers services when everything is 20-50/mo

Using cron jobs in RedwoodSDK to post this post on schedule to X. Say post one more time. RedwoodSDK works with @Cloudflare scheduled tasks. 🔥

We are a group of developers that come from the world of Rails, Django, and Laravel. But we have always loved coding in JavaScript more than Ruby, Django, and PHP. When designing RedwoodSDK, we leaned into what we love about TypeScript. And that's exactly why we pick Cloudflare because it uses browser-native APIs to communicate with services. We doubled down on this and decided that if the browser provided an API, we would work alongside it, not abstract or co-opt it. So it's not Postgres, abstracted by JS. Or JS abstracted by Next. It's a framework that is TypeScript. It literally gets out of your way: So you can focus on your code, not the framework or the platform that it runs on.

The weekend's almost over. Just one more deploy before bed

The secret to scaling is always caching. h/t ⁦@hyperknot⁩ blog.hyperknot.com/p/openfre…

The new branding for @RedwoodJS has been so fun to put together.

Feels like @RedwoodJS is the JS spiritual successor of Laravel. All batteries included, similar routing/middleware logic. I think they're onto something

Workers KV keeps getting faster. Speed and reliability tend to show up to the party together Top = new first-party system Bottom = old third-party system details in the blog post

RedwoodSDK is to Cloudflare + React what SchadCN is to UI. Addons for everything: Blog, auth, changelog. Plug in, compose, fork, remix.

🤯 Major Sandbox SDK update! Build AI agents, CI runners & more with live streaming, code interpreters (Python & JS!), Git support, & process control—all without infrastructure management. 🚀 Level up your Workers! developers.cloudflare.com/ch…

Pre-order now! Shipping v1.0 in early October 2025

one of the most direct user facing teams in the Workers org! 👇

Cloudflare's `waitUntil` is a blessing: It allows you to execute a function after you have returned a response. Insanely helpful if you have to kick-off an asynchronous task and don't need a user to hang around for it to complete.

Every feature is an addon in RedwoodSDK. Need a blog? Add it. Auth? Drop it in. Changelog? Plug and play. Mix and match your stack, piece by piece. Like plugins for React on Cloudflare! No magic, just code. shareware.dev

Use RedwoodSDK

It just hit me. AI generates overly complicated code because it was trained on that, in other JS frameworks. This simple example of uploading media to @Cloudflare R2 proves my point. Below is how we do it with RedwoodSDK, the POST method is based of other frameworks... Really frustrating sometimes

Fact: You already know RedwoodSDK. Why? Because it's based on TypeScript, the browser and the network. Request in/ Response out.

We did it. We shipped Server-Side-SPAs. SSR+RSC+Websocket > Pretending to be a browser youtu.be/IjplRRpIogE HTML isn't the problem. Javascript isn't the problem. Emulating the browser was.