 All right, our next speaker is yet another Brendan. His name is Brendan Irvine-Broke. He is the product manager of Cloudflare Workers at Cloudflare, where he leads the workers' runtime team. Prior to this, he was part of the engineering leadership at Misco and Intercom, and is a former Y Combinator startup founder. Today, he'll be sharing on deploying Wasm to the edge. Please welcome Brendan. Hi, everybody. So my name is Brendan. I work on Cloudflare Workers at Cloudflare, and I want to just give you a little overview of some of the things that we're working on right now around WebAssembly. But sorry to disappoint you to start. I'm here to talk a little bit about some very boring technologies decisions that we've made and actually how those help us give you a little bit more leverage and connect back to some of the exciting standards that I know we're all talking about today. And so those two that I'll be talking about later are Witt and Witt Bynjen, which we're really excited about, and I'd love to talk to folks after. But before I do that, I have a saying that I go back to really frequently. It's a mantra called run less software, and I picked this up from an engineering director who I used to work with. An idea is like trying to remove undifferentiated heavy lifting, like kind of grunt work, and to really fight to manage fewer pieces. And that's, I think a lot of why we're all here, we're trying to make things more portable to remove a lot of the craft. Brendan, big shoes to fill, was talking a little bit about APIs from the 1970s and how do we get away from them. And so for those who aren't familiar, Cloudflare has a full stack serverless developer platform. We have kind of workers for serverless compute, a number of databases, et cetera. And this is all kind of globally distributed and serves many, many, many millions of requests per second right now. So all over the world. And so workers is fundamentally a web interoperable runtime. And that's really important to us. I know I'm in a room of people who are working on interesting new run times and ecosystem things that are kind of breaking out of where WebAssembly got its roots in the browser. But we're built on top of V8. And we really think that gives you the power of the web platform and web standards, but in a serverless context. And so the way that we do this right now is we have a project called Worker's RS. Rust bindings make it possible to write a worker 100% in Rust. So we make really heavy use of WasmBindGen, the web sys module within that to make that happen. And so run through a little basics looks kind of like this. This is a kind of worker that lets you fetch something from our KV store and then return a response. Pretty simple. There's a lot of people building similar things like this. But WasmBindGen really allows us to shift really fast and make APIs available in JavaScript and then get them available in WebAssembly on a really quick timeline. Another example, this is talking to D1, which is our SQL database. And so this all works today. There's people using this in production, relying on it at scale all around the world. So that's the boring stuff that works out of the box. But we have this kind of idea of being web interoperable. If you can do it in a web browser, why not in a serverless function? And so some of what we're working on right now is taking some of the exciting APIs that are growing in web browsers that I think really have a strong feature and making them available in a serverless context. So one example of that is the WebGPU API. So this launched really a couple of months ago. I know people have been working on it for years. But we're working on adding this to the worker's runtime itself so that you can make use of a GPU. And this works today. Check out the open source worker's runtime cloudflare slash workerd. And so you might be asking like, well what is this JavaScript API have to do with WebAssembly, like why are you talking about it at a WASM conference? But the thinking here is like the more of these that we can support, the faster we can make really interesting capabilities available in a serverless function from WebAssembly via bindings. And so what are the other things that are part of the web platform today that if you could support them in a serverless function, things like web transport, things like the WebRTC APIs from browsers, like what are the things you could build for a globally distributed application all over the world? And so I was talking about WASM bind gen before. There's also publishing wit specifications, wit definitions and kind of using wit bind gen to move a layer beyond that so that we're not kind of having to write bindings on a kind of language specific basis. And so, you know, weboperability really gives us like a lot of leverage, like a lot of portability across client and server. And that's where we think the opportunity really is. So I mentioned WASM bind gen, like writing bindings for each language, obviously an unsustainable thing for everybody in order to support the broad set of languages that we know that developers want to bring to WebAssembly. And so, you know, what we're increasingly thinking about is like what are the things that we can publish to make it easier for people to build their own bindings on top of Cloudflare? What are the interesting proposals that are happening around kind of on top of WASI? What are the standards of like, how do you talk to a key value store in a way that's portable across platforms? And so we're excited about all of these new standards. We love your feedback on workers. A lot of the reason why we're here at this conference is to talk to all of you and for you to tell us like what do you want out of Cloudflare's platform? So love to meet as many of you in the hallway, just free to say hi. And thanks for your time.