Yes. So I think that I am not very bullish on if the only thing that edge computing delivers to you is it's a little bit faster. That's a very big market. And I spent, like Tom at Akamai says that Akamai has been doing edge computing longer than anyone else, and that's true. They have. They launched the first true edge computing platform back in 2001. Danny, one of the co-founders, designed the entire thing. It was amazing. It ran .NET and Java, which were the 2 dominant languages at the time. And the pitch for it was, it's a little bit faster, and it's going to shave 100 milliseconds off of network latency, and that was a big deal. And yet somewhere in the sort of late 2000s, they basically shut it down.And the question was why. And I spent a bunch of time tracking down all of the old engineering managers and product managers that built that platform and saying what went wrong. And the answer time and time and time again was that just being a bit faster didn't compensate for the challenges that having something that developers have to think about my code is running not in one place but in many places all around the world.And I think that, that really has informed a lot of how we have thought about it in 2 different ways. The first was a recognition that just being a little bit faster, yes, there are certain applications, credit card processing, human-computer interaction. There are some things that it matters but it's maybe $100 million market. It's just not that big a market that exists out there.And then the second is that developers are super lazy. And I know this because I used to be a developer and we're all super lazy. And so they want to do things that are really easy to use. And so that means that like you have to focus on ease of use as the critical function. And so I've kind of coined this idea of, there's Maslow's hierarchy of needs, and so Matthew's hierarchy of developer needs. Like self-actualization in Maslow's hierarchy of needs, the very top of the pyramid, that's speed, right? That's the nice-to-have we all aspire to eventually. But the thing that's more important than speed is consistency. I have light switches in an apartment that I have where you flip them on and it takes 3 seconds for the lights to turn on, but it's always 3 seconds. And so you can adapt to it. So you just sort of, the first time you're over in my house, you're like, flip the light switch on and you think it's broken. But what would be worse than it taking 3 seconds is if it sometimes it was instant and sometimes it was 3 seconds because anyone didn't quite know what to do, right?And so actually, consistency is more important than speed. Cost is more important than consistency. The reason that I have these light switches is I was cheap, and so I didn't upgrade to the more fancy light switches. So it turns out, just like developers, cost is going to beat consistency and people will pick what's cheaper. More important than cost is ease of use because developers are lazy. And so we have really focused on, yes, we're the fastest and we're the most consistent and we're the most cost effective, but if we don't nail ease of use, then this could be a niche platform. So we're really focused on how we build out the ease of use. And the only thing that trumps ease of use is actually the really boring but foundational food, clothing and shelter, which is regulatory compliance if you're a CIO that's out there.And so that's the one thing where you can find some incredibly amazing new developer platform, which is really fast and really consistent and really cheap and really easy to use. But if it's hosted in North Korea, like it's going to be a nonstarter for JPMorgan to be using it. And so I think that what we really think of as, yes, fast is great and consistent is great and cost-effective is great, but we've got to nail ease of use.And where I think the real killer functions come from is actually that compliance piece because I think more and more countries and even down to states are going to be saying, a user's data has to stay in this particular region and be processed in that particular region. And that means that if the first thing that you're doing when you're using your cloud platform is picking what region you're using, then you're doing it wrong. Whereas in Cloudflare's case, you write what code once, you label the data and say that data has to stay in that particular region and then the application just works and makes sure that you're complying with whatever it is that you have, your obligations are around the world.