RedwoodSDK

@ZubairIbnZamir @wakujs do it!

Every JS framework should ship an official e-commerce example—covering state management, effects, database integration, auth, and other real-world concerns—so we can see proper production-grade patterns instead of guessing. @wakujs @RedwoodJS

@dillon_mulroy fancy

OH: “Do you know anything about wine” “Yeah, I worked at trader joe’s”

tracking here: github.com/redwoodjs/sdk/…

these "changes" are isolated per user. So everyone that uses your software can customize it.

Noodling on something new. RedwoodSDK framework can now edit itself, completely inside of workers.

@MattieTK got rate limited :/

Okay, while I iron (and/or until my wife notices) I'll let you all mess about with this lamp.tk.gg Cloudflare Worker → Mesh → Raspberry Pi → Hue Hub → Hue Socket → Lamp

the artifacts + agents sdk + dynamic workers + isomorphic-git combo is over powered

It's kind of crazy how much of the way we've been designing Workers over the past 9 years unexpectedly turns out to be so relevant to AI and agents. Durable Objects and lightweight isolate sandboxes are obvious big things. But there are subtler things. Consider "bindings". In Workers, our environment (`env` object) doesn't just contain strings. It can contain live objects, which we often call "bindings". For instance, a Workers KV binding is a live object representing a Workers KV storage namespace. Once you've configured it, you can just do: let val = await env.MYKV.get("foo") await env.MYKV.put("foo", "new value"); Notice: There's no connection string. No secret token that you have to pass to talk to your KV namespace. The Workers Runtime handles it for you. You just get an already-initialized client object, on which you can call methods. You can still do everything you want to do. But you know what you can't do? Leak the secret token. Because there isn't one. A KV namespace binding fundamentally cannot be "leaked" because it's not bytes. But over the years, a lot of people have questioned whether this really mattered. I've had people inside and outside the team say: "Why are you so weird, Kenton? Yeah sure it can't leak but now I have to learn this new way of thinking about things. No other runtime works this way so writing portable code takes extra work. I'd rather just stick to what I'm used to, and anyway I know better than to leak my environment variables." Well, now we have AI agents writing the code and... suddenly everyone is worried about agents leaking keys. People are creating convoluted schemes to intercept the outbound traffic and inject keys in a proxy, or trying to issue very-short-lived keys so that if the agent leaks them the window of attack is short. Ahem. Welcome, folks! We solved this 8 years ago! Here's an old blog post -- written when I personally was still very much Not Thinking About AI -- which seems so much more relevant now: blog.cloudflare.com/workers-enviro…

@Qnoox @dillon_mulroy

@RedwoodJS @dillon_mulroy

trying something new out tonight

Cloudflare refunded everything! Amazing company and fast service ❤️

@jasperfurniss @dillon_mulroy ask your agent to give it a shot and let you know!

@dillon_mulroy I’ve always wanted to give it a shot. Curious to see how it is for you.

@Qnoox @dillon_mulroy who even writes code?!

@dillon_mulroy you had me until react 😭

Yep. Build the right primitives early to go faster in the long run. We didn't bet on big VMs or k8s or traditional hyperscaler tech. Took the harder — and certainly less obvious — road to set ourselves up for the future.

@darkmembo @CloudflareDev Nice! Now all we need is a vibe platform!

there is no better infra today than @CloudflareDev for your vibe-platform

@rwdaigle @Cloudflare we're doomed

If you’re not mainlining all of this week’s @Cloudflare blog posts straight into your coding agent of choice, you’re ngmi

@jessmartin @rwdaigle @Cloudflare this guy is c-level

@rwdaigle @Cloudflare passing blog post to my agent is new engineering pipeline i'm like that tech CEO emailing his CTO "did you see this? what are we doing about it??"

Does the Prince even know about us?

@simonxabris @dillon_mulroy @elithrar @mattzcarey @thomas_ankcorn if you're gonna milk a cow it might as well be full-fat and durable.

@dillon_mulroy @elithrar @mattzcarey @thomas_ankcorn This week really has cemented this meme

announcing artifacts - a versioned file system that speaks git certainly the coolest thing i've ever built and i got to build it with some truly great people fearless leader: @elithrar zig/git nerd: @mattzcarey storage goat: @thomas_ankcorn blog.cloudflare.com/artifacts-git-…