 um, developer tools. Okay. Um, the, uh, this is, this really got interesting with, with two things. Xcode cloud is really kind of blew me away, especially when I dug into it watching the state of the union. So yes, Xcode Xcode cloud, boy, man, let's say that 10 times fast. Um, they must have rehearsed this, uh, cause I'm having trouble with it. Xcode cloud is a, uh, allows you to collaborate for sure. And that's what it sounds like it is when you hear the name, or at least that's what I thought it was when I heard the name. It was some sort of cloud collaboration thing. And that's awesome. But that any, yes, it has that in there. However, that's not what Xcode cloud is. What Xcode cloud is, is you getting to leverage Apple servers to build your apps and do all of your UI and unit testing and all of that without doing it on your computer and also without leaving Xcode. So you could, and you can set all this stuff to happen as a developer, you know, you push a change and you can have it build on every push if you want. And my guess is because you're using Apple servers to do your builds that they're going to happen way faster than you could probably do them in your own offices. So one little piece of this that I puzzled about, and I still don't know the answer to it. And this may be my lack of, of understanding of all these, the different pieces of this chain. But specifically it sounded like I could run tests on every single device that Apple makes and historically has still continues to support, not has ever made but continues to support without my having to go out and buy 17 different iPhones and iPads and Macs. Am I, did you get that sense? Absolutely. Yeah. And you can set it to do those tests on every build or whenever you want it to, like you don't have to stop and say, Hey, go do these tests. And also if you have, they use an example of, you know, when you have an intermittent bug, right, one that crashes sometimes, but not all the time, you can have it. I think by default, it runs a test until it hits a crash. You can have it run a test a hundred times. And if you get a crash 50% of those, well, that gives you different information, right? And, and you get full screenshots of it being tested on all devices in all different modes, portrait, landscape, dark mode, light mode. I, I realized for us as users, we don't really care about this. However, knowing what it is like to be focusing on doing your development or doing anything that is immersive and then having to back out of that to do a build and wait for the build server and wait for your tests and, okay, it's all in the same computer. So now my CPU is like skyrocketing. I think this, I think it's possible we may not be able to give this enough of a, of a highlight to really show the difference that it's going to make long term. I think this is huge. Huge. Huge. It's not my favorite thing of the developer tools, but go ahead and you say, because I know you got two on your list. Okay, well, my second one was, was Swift concurrency. Really? You don't have my number one thing on your list. That's the beauty of having three of us here. I may have it on my list. But that's that's the beauty of having three of us here. Just, and I know that's one of those. The concurrency thing is just one of those things. I've heard developers complain about the ones that say, I don't want to move to Swift because concurrency is a difficult thing to do. It's convoluted. I want to be able to have stuff run on separate threads. And the examples that they showed in the state of the union made it very obvious that the whole multithreading of Swift is is brought yet more to a first class citizen, which I I'm hoping that the developers that were complaining about moving to Swift because of this, actually now move to Swift and don't just find something else to complain about. I just wrote a big audio processing app in Swift. So all and all of this is Swift. And I had to deal with a bunch of concurrency issues. And, you know, dispatch queues and yeah, you know, your interface has to run on the main and all that stuff. That and I honestly, when I started, I really didn't know my way around all the different dispatch queues and what to use when and, you know, how to how to set really how to wrap things properly. And so I ended up making a lot of mistakes. And it's testing can be with concurrency can be really difficult because it's hard to know what's, you know, suddenly why did that cause it to crash, right? It's not tied to a piece of user interface, right? You didn't push a button and it crashed. It was, you know, four processes running at the same time. And they, you know, sometimes they would run into each other and sometimes they wouldn't. So I love this concurrency to make to simplify it because it really is some really naughty code. Yeah. But it wasn't my favorite thing. Well, that's why I always like writing embedded code, because typically embedded code is single threaded. Well, right, right? Multithreaded code. The possibility for disaster grows exponentially, as I'm sure you've found because, oh, now I got to keep track of 100 things happening at once versus one. And then again, having multiple cores and being able to do multiple things at once is cool as long as it's managed properly. We as users like apps that run with concurrency as developers as developers, we like the simplicity. Yeah. So, John, you're, I'm waiting for that other shoe to drop. What's the, what's the other thing you were getting? I think they mentioned something about being able to develop apps on the iOS device. I think you've got it. Not, well, almost. Not on iOS, but on iPadOS. Or iPadOS, yes. Okay. Yeah, playgrounds. Playgrounds on iPadOS are now, I've been saying this for so long that, that the iPad will never be my main machine until I can build an app and put it on the app store with that machine. Because if I have to, if I have to go back to back OS and write all my code, you know, all that stuff, then I might as well just work on my Mac. And now I'm like, wow, playgrounds on an iPad, which you've always had, playgrounds on an iPad, but playgrounds on an iPad where you can, without touching a Mac, you can hit submit and put your app on the app store. That's amazing. I think that's gigantic. Oh, that's huge. Yeah. No, you're right. It is bigger than concurrency, for sure, because it opens the door for so many people in so many different ways. Yeah. And I really wasn't judging the relative merits of them. I just, I just wanted to include that one. Of course. Yeah, that's why that's why we're all here. Yeah. Yeah. No, the, for clarity, you can build iOS and iPad OS apps with Swift Playgrounds on iPad. So you can't build Mac OS apps in Swift Playgrounds on iPad yet. Yeah, yet. Yeah. Yeah. Fair. Although you're going to be able to build an app. I would almost guarantee this. You're going to build an app. It's going to, it's going to be buildable on an iPad. You're going to build it in Swift UI and some future version of Swift UI. And it's going to have all, it's going to have all the Mac elements you need to build an app that maybe won't run as natively or as pretty or as perfectly as your Mac apps run, but that'll run on a Mac and someone who wasn't sophisticated would run it and think it was built in a native Mac app. Yeah. I believe that's true. I believe it's coming eventually, if not, you know, next year, maybe the year after. Yeah, fair. Fair.