Joined July 2019
454 Photos and videos
1
4
595
RedwoodSDK retweeted
machinen.dev/ - boot once, run everywhere. A MicroVM that runs on hardware you already own. Close your laptop and it hands off to another host. Works across macOS, Linux, and Raspberry Pi. (aarch64)
19
45
289
19,253
Noodling on something new. RedwoodSDK framework can now edit itself, completely inside of workers.
2
1
5
1,012
these "changes" are isolated per user. So everyone that uses your software can customize it.
1
376
RedwoodSDK retweeted
the artifacts agents sdk dynamic workers isomorphic-git combo is over powered
18
7
274
23,562
RedwoodSDK retweeted
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-…
28
49
531
87,759
RedwoodSDK retweeted
Apr 16
wtf is in the water at cloudflare?
6
18
431
23,104
RedwoodSDK retweeted
Cloudflare refunded everything! Amazing company and fast service ❤️
I love @Cloudflare but it's getting to AWS levels of mysterious billing I have no clue which site has "Smart Shield Argo" enabled and since I have like 200 sites in Cloudflare, I have no way to figure this out There's also no Argo in Usage, and apparently I been paying this for months now without even wanting or using it 🤷
75
13
1,255
135,926
RedwoodSDK retweeted
trying something new out tonight
18
5
257
18,113
RedwoodSDK retweeted
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.
you can tell that workers/v8 is the right primitive for agents by how fast cloudflare keeps shipping core infra
2
8
110
10,383
Does the Prince even know about us?
2
354
RedwoodSDK retweeted
Alarms in durable objects are pretty neat. Playing around with CloudFlare, it's super simple to set an alarm per user (if your users have a DO each). Here I have a DO per user, and an alarm (schedule) per person. Trigger code, when you want, keeping the state close to my user. I added this new pattern to the GitHub repo below, in case anyone was interested too.
3
3
36
2,857
RedwoodSDK retweeted
5 years of building out the foundations and primitives of the workers platform that has now paid off and enables our teams to rapidly build best in class products and deploy them to region earth for our users
what's in the water over there, y'all are shipping some awesome work
2
5
117
12,555
RedwoodSDK retweeted
This week really has cemented this meme
5
11
181
10,566
Try this right now! For an existing rwsdk project, users just need to update two dependencies in their package.json: pnpm add -D @cloudflare/vite-plugin@1.31.0 wrangler@4.80.0 Or with npm: npm install -D @cloudflare/vite-plugin@1.31.0 wrangler@4.80.0 These are peer dependencies of rwsdk, so they're listed directly in each user's project. The starter template already ships with these versions for new projects.
A little late to the party but we're also launching a Cloudflare Local Explorer, and a new initiative to build a comprehensive `cf` CLI for the whole of Cloudflare. Local explorer gives you the ability to inspect and edit your local resources when building apps on Cloudflare...
1
1
9
1,307
RedwoodSDK retweeted
A little late to the party but we're also launching a Cloudflare Local Explorer, and a new initiative to build a comprehensive `cf` CLI for the whole of Cloudflare. Local explorer gives you the ability to inspect and edit your local resources when building apps on Cloudflare...
9
13
186
27,319
RedwoodSDK retweeted
You can run Github actions workflows fully locally with Agent CI. Nice work @appfactory, such a crazy good unlock for coding agents!
5
10
104
7,314
RedwoodSDK retweeted
Apr 10
Try @RedwoodJS you'll fall in love
1
1
5
600