1 00:00:03,323 --> 00:00:05,423 Welcome to another episode, empower Apps. 2 00:00:05,423 --> 00:00:09,953 I'm your host, Leo Dion here live at Community Kit. 3 00:00:10,283 --> 00:00:11,573 It's an exciting day. 4 00:00:11,603 --> 00:00:12,323 Dub dc. 5 00:00:12,653 --> 00:00:15,143 Also with me is Matt Mascot. 6 00:00:15,233 --> 00:00:19,163 Matt, thank you so much for coming on the show again in Live and in Person. 7 00:00:19,223 --> 00:00:20,873 Thank you very much, Leo, for inviting me. 8 00:00:21,353 --> 00:00:25,023 So we're gonna talk about the stuff that was revealed today, we probably 9 00:00:25,023 --> 00:00:28,953 haven't had a chance to open up Xcode, but before we do that, I'll let you 10 00:00:28,953 --> 00:00:30,448 go ahead and introduce yourself. 11 00:00:30,808 --> 00:00:31,018 Sure. 12 00:00:31,018 --> 00:00:31,378 Thank you. 13 00:00:31,378 --> 00:00:34,668 My name is Matt and, been a long time Apple developer. 14 00:00:34,848 --> 00:00:38,238 I have this like hyper-specialization now working in swift concurrency, 15 00:00:38,238 --> 00:00:40,818 but I still pay attention to lots of other stuff that are going 16 00:00:40,818 --> 00:00:40,998 on. 17 00:00:41,678 --> 00:00:42,128 Awesome. 18 00:00:42,278 --> 00:00:46,128 So yeah, what's your initial reaction from everything? 19 00:00:47,333 --> 00:00:50,353 Okay, so I'm very interested in the technical details and I was 20 00:00:50,353 --> 00:00:53,733 hoping for Some more technical stuff going into the state of the Union. 21 00:00:54,383 --> 00:00:54,533 And 22 00:00:54,543 --> 00:00:58,013 so I wanna like now look more at the APIs and see what kind of stuff are actually 23 00:00:58,013 --> 00:00:58,583 introduced. 24 00:00:59,188 --> 00:01:02,218 Yeah, I think that's the same thing here is it's, there's a lot of 25 00:01:02,218 --> 00:01:05,608 fascinating stuff that we'll go over today, but I also think at the same 26 00:01:05,608 --> 00:01:09,238 time, I really wanna get my hands dirty and try it out with Xcode and stuff. 27 00:01:09,898 --> 00:01:12,208 I'll just start off talking about some of the stuff that I found 28 00:01:12,208 --> 00:01:13,828 fascinating just from the keynote. 29 00:01:14,288 --> 00:01:16,028 we got foundation models. 30 00:01:16,308 --> 00:01:19,488 What's been heavily rumored and on everybody's wishlist is we actually 31 00:01:19,488 --> 00:01:23,418 have LLM models to work with and. 32 00:01:25,218 --> 00:01:28,038 The apps in our app development, but also there's a lot of 33 00:01:28,038 --> 00:01:29,988 stuff in Xcode that looks cool. 34 00:01:30,048 --> 00:01:31,128 That might be useful. 35 00:01:31,623 --> 00:01:35,283 Yeah, it looks like it supports a very live, interactive coding system, 36 00:01:35,283 --> 00:01:36,693 which I think a lot of people enjoy. 37 00:01:37,068 --> 00:01:39,078 Also, you can plug into other lms. 38 00:01:39,128 --> 00:01:40,568 Which sounds really great. 39 00:01:40,568 --> 00:01:44,268 As a fan of stuff like Cursor and Claude, I'm really looking forward 40 00:01:44,328 --> 00:01:45,648 to playing around with that. 41 00:01:46,368 --> 00:01:47,838 the intelligent shortcuts. 42 00:01:47,868 --> 00:01:50,518 So have you worked with, app intents at all? 43 00:01:50,623 --> 00:01:51,643 Only a little bit. 44 00:01:51,693 --> 00:01:53,613 So that looks really interesting. 45 00:01:53,613 --> 00:01:58,053 We've been hearing over the last few years guys, start implementing app intents. 46 00:01:58,053 --> 00:01:59,553 Start implementing app intents. 47 00:02:00,033 --> 00:02:03,383 And this feels like the first taste of this is why they've been 48 00:02:03,383 --> 00:02:05,093 telling us to do that for so long. 49 00:02:05,633 --> 00:02:09,713 And then the other thing that we've been wanting for the last, 50 00:02:09,893 --> 00:02:13,403 15 years is Windows in iPad. 51 00:02:14,003 --> 00:02:15,623 How excited are you about that? 52 00:02:16,928 --> 00:02:20,768 I'm a very casual iPad user, but I know people are excited and I'm 53 00:02:20,768 --> 00:02:22,028 excited too for them to get what they 54 00:02:22,028 --> 00:02:22,358 want. 55 00:02:22,523 --> 00:02:24,173 You're an iPad movie watcher, aren't you? 56 00:02:24,188 --> 00:02:24,308 watcher. 57 00:02:24,308 --> 00:02:28,778 I'm really interested in how like sharing drag and drop that kind of 58 00:02:28,988 --> 00:02:32,528 like windowing is a good, very good solid step and I'm gonna install 59 00:02:32,528 --> 00:02:34,298 it tonight probably and try it out. 60 00:02:34,298 --> 00:02:39,178 But to me, like the interactions between the, the different apps, 61 00:02:39,508 --> 00:02:41,638 'cause we just have the share sheet and we have drag and drop. 62 00:02:41,668 --> 00:02:45,988 That to me is like the next step of, and seeing how well that works in this 63 00:02:45,988 --> 00:02:49,408 new paradigm that we have with OSUI, 64 00:02:49,913 --> 00:02:54,298 I think that Apple's clearly experimented a lot with user interface 65 00:02:54,298 --> 00:02:56,898 paradigms with iPad os Over the years. 66 00:02:56,958 --> 00:02:57,858 And I think that's great. 67 00:02:58,008 --> 00:03:01,578 And it's also nice to see that after all this different experimentation, they've 68 00:03:01,578 --> 00:03:05,388 come back to something so familiar because it's totally possible if the o, it could 69 00:03:05,388 --> 00:03:08,208 have gone the other way, that they hit on something very different that works well. 70 00:03:08,208 --> 00:03:10,218 And maybe that came towards the Mac, for example. 71 00:03:10,263 --> 00:03:13,728 I don't know how I. I dunno how else they could possibly do it. 72 00:03:13,728 --> 00:03:18,128 Like that's what I'm seeing is we see this, we've seen other things, tried 73 00:03:18,128 --> 00:03:21,698 stage manager, all that stuff, and at the end of the day, yeah, that's what 74 00:03:21,698 --> 00:03:23,738 they've come back to is windowing. 75 00:03:24,858 --> 00:03:25,938 We have to talk about it. 76 00:03:26,448 --> 00:03:31,998 I'm sorry, but what's been rumored for the last few months? 77 00:03:32,218 --> 00:03:35,278 The thing that's not Apple intelligence and that is a new glass design. 78 00:03:35,328 --> 00:03:35,988 What do you think? 79 00:03:37,383 --> 00:03:38,643 I didn't get a good enough? 80 00:03:38,643 --> 00:03:40,263 I feel like I need to actually use 81 00:03:40,263 --> 00:03:40,503 it 82 00:03:40,843 --> 00:03:42,733 To make a real, to have a real opinion 83 00:03:42,788 --> 00:03:43,508 Yes, exactly. 84 00:03:43,553 --> 00:03:47,303 there was a lot of motion effects that you saw, and that's very interesting to me. 85 00:03:47,393 --> 00:03:52,193 Many people have been worried about readability and contrast and it looks 86 00:03:52,193 --> 00:03:53,903 very justified with what we saw. 87 00:03:54,143 --> 00:03:56,633 So I'm hoping that isn't as bad as it looked like it could be. 88 00:03:56,918 --> 00:04:00,638 Or at the very least, we have a bunch of accessibility modifiers that 89 00:04:00,713 --> 00:04:01,073 sure. 90 00:04:01,073 --> 00:04:01,283 I'm 91 00:04:01,283 --> 00:04:02,363 sure that will be there. 92 00:04:02,413 --> 00:04:04,543 Are you gonna try and chime and see how it works? 93 00:04:05,308 --> 00:04:07,948 Yeah, actually I'm very interested in particular how it looks in 94 00:04:07,948 --> 00:04:09,658 Mac Os and how it affects MAC OS 95 00:04:10,063 --> 00:04:10,303 Yeah. 96 00:04:10,343 --> 00:04:11,033 Yeah, same here. 97 00:04:11,813 --> 00:04:15,983 So I recently, right before I left, I got a Mac Mini M four I. 98 00:04:16,503 --> 00:04:19,653 Like another computer because I need another Mac for my CI stuff. 99 00:04:19,953 --> 00:04:23,403 I think I'm gonna put, Tahoe, which is the new code name. 100 00:04:23,403 --> 00:04:26,283 I'm gonna put it on there and test out my apps on that and see how it works. 101 00:04:26,283 --> 00:04:27,393 'cause I'm really curious. 102 00:04:27,423 --> 00:04:28,203 Yeah, that makes sense. 103 00:04:28,533 --> 00:04:31,563 So one thing I know besides concurrency that you're 104 00:04:31,563 --> 00:04:34,253 enthusiastic about is, text kit. 105 00:04:34,283 --> 00:04:34,733 Yes. 106 00:04:34,898 --> 00:04:36,998 now we got all this new, attribute. 107 00:04:36,998 --> 00:04:42,698 So they have all this new attributed string stuff that's been added to Swift 108 00:04:43,208 --> 00:04:47,018 Does that help you at all, or are you like, no, this isn't, cut it for me. 109 00:04:47,118 --> 00:04:51,198 My suspicion is that it will be absolutely insufficient for editing 110 00:04:51,198 --> 00:04:55,998 large documents or doing sophisticated more than just having like basic, 111 00:04:56,128 --> 00:04:57,988 user input and changing a string. 112 00:04:58,273 --> 00:04:58,423 Okay. 113 00:04:58,423 --> 00:04:59,563 it'll support anything like that 114 00:04:59,583 --> 00:04:59,843 Okay. 115 00:05:00,428 --> 00:05:03,398 there was a bunch of new APIs that looked like they added, at least 116 00:05:03,398 --> 00:05:09,878 on the iOS end for maybe not text editing, but just being able to build. 117 00:05:10,568 --> 00:05:13,008 I know it'll be interesting to see, once we play around 118 00:05:13,008 --> 00:05:14,748 with it and see what we get, 119 00:05:15,438 --> 00:05:19,188 and I know many people have the need for a rich text editing experience, 120 00:05:19,188 --> 00:05:20,448 Does it, is it enough for them? 121 00:05:20,538 --> 00:05:21,318 Yeah, exactly. 122 00:05:21,438 --> 00:05:21,738 All right. 123 00:05:21,738 --> 00:05:24,138 Let's get into, unless there was something else you wanted 124 00:05:24,138 --> 00:05:25,578 to mention about the keynote. 125 00:05:25,578 --> 00:05:28,548 I just had stuff about CarPlay, which I'm a big fan of CarPlay. 126 00:05:28,578 --> 00:05:29,148 I love it. 127 00:05:29,313 --> 00:05:30,993 Yeah, and it sounds like it got a lot of attention. 128 00:05:31,118 --> 00:05:34,808 We've been hearing a lot about CarPlay Ultra on some of the models. 129 00:05:34,908 --> 00:05:36,018 Renting vehicles. 130 00:05:36,058 --> 00:05:38,248 I miss CarPlay, I can tell you that. 131 00:05:38,278 --> 00:05:41,518 And, it was cool to see, it looked like it was the interface that they were 132 00:05:41,518 --> 00:05:45,288 demoing, by the way, looked exactly like the interface on our Ford, transit. 133 00:05:45,348 --> 00:05:45,618 Oh, okay. 134 00:05:45,918 --> 00:05:48,938 So I was like, I recognize that, that looks like my, mini bus 135 00:05:49,003 --> 00:05:50,053 Widgets on a CarPlay. 136 00:05:50,103 --> 00:05:51,093 That sounds awesome. 137 00:05:51,098 --> 00:05:54,848 I wanna, I definitely, it's on my bucket list to play around with CarPlay. 138 00:05:54,848 --> 00:05:56,138 I have a lot of good ideas. 139 00:05:56,258 --> 00:05:57,188 Hold assist. 140 00:05:57,248 --> 00:05:58,178 Looks really great. 141 00:05:58,478 --> 00:05:58,958 Finally. 142 00:05:58,958 --> 00:05:59,318 I'm glad to 143 00:05:59,318 --> 00:05:59,468 see 144 00:05:59,483 --> 00:05:59,903 I missed that. 145 00:05:59,903 --> 00:06:00,503 What is this? 146 00:06:01,028 --> 00:06:06,878 Okay, so when you're on hold, it can either detect, hold music or 147 00:06:06,878 --> 00:06:11,038 something, but basically it can, it will let you know when you're on 148 00:06:11,038 --> 00:06:13,138 hold and somebody finally picks up. 149 00:06:15,008 --> 00:06:18,528 There's like a new wrist flick, interaction on the watch, which 150 00:06:18,528 --> 00:06:21,198 I love because I don't always have two hands available to me. 151 00:06:21,318 --> 00:06:22,008 Yeah, that's cool. 152 00:06:22,338 --> 00:06:27,408 And I am looking forward with trying out the iPhone karaoke, feature in 153 00:06:27,408 --> 00:06:29,588 TVOS, especially with the kiddos. 154 00:06:29,978 --> 00:06:31,478 So we'll see how that works out. 155 00:06:32,838 --> 00:06:34,578 Okay, so State of the Union. 156 00:06:35,148 --> 00:06:36,858 Anything you wanted to talk about the state of union or 157 00:06:36,858 --> 00:06:37,998 should I just go through my list? 158 00:06:38,328 --> 00:06:39,018 Go through your list. 159 00:06:39,018 --> 00:06:40,158 I'm sure we can pick up stuff. 160 00:06:40,218 --> 00:06:40,248 Okay. 161 00:06:41,168 --> 00:06:45,518 About the glass design, we have, the colors informed by the context. 162 00:06:45,878 --> 00:06:47,198 It's curved with the display. 163 00:06:47,198 --> 00:06:48,758 A lot of mentions about that. 164 00:06:48,758 --> 00:06:49,388 Absolutely. 165 00:06:49,628 --> 00:06:52,448 constancy, is that the word constancy? 166 00:06:52,508 --> 00:06:54,068 They used that word quite a bit. 167 00:06:54,228 --> 00:06:55,008 didn't notice that 168 00:06:55,008 --> 00:06:55,578 Okay. 169 00:06:55,758 --> 00:06:56,508 That was weird. 170 00:06:56,698 --> 00:06:58,438 It automatically updates with recompile. 171 00:06:58,468 --> 00:06:58,768 Okay. 172 00:06:59,068 --> 00:06:59,938 Here's a question. 173 00:07:01,513 --> 00:07:08,773 Is this, was there something through this new glass design that they are trying to 174 00:07:09,343 --> 00:07:13,003 hint at possible new models of the iPhone? 175 00:07:13,073 --> 00:07:13,313 Okay. 176 00:07:13,313 --> 00:07:13,823 I'm gonna wait. 177 00:07:13,853 --> 00:07:15,353 I wanna put that question on hold for one second. 178 00:07:15,353 --> 00:07:18,203 I want to call out something else that you just said, which was you have to 179 00:07:18,203 --> 00:07:20,813 recompile to get to pick up these changes. 180 00:07:20,813 --> 00:07:24,833 And I, that was interesting to me because presumably the reason they're 181 00:07:24,833 --> 00:07:27,798 doing that is they're putting this check in to make sure that you have 182 00:07:27,798 --> 00:07:31,188 at least built through app once they're not opting existing apps in. 183 00:07:31,258 --> 00:07:34,138 So I think if you have an app that you don't update, it will not 184 00:07:34,138 --> 00:07:35,968 receive these new UI treatment. 185 00:07:35,968 --> 00:07:36,118 Yeah. 186 00:07:36,118 --> 00:07:36,238 It 187 00:07:36,323 --> 00:07:36,443 does. 188 00:07:37,348 --> 00:07:38,548 Has that always been the case? 189 00:07:38,598 --> 00:07:40,278 That kind of thing has happened frequently. 190 00:07:40,288 --> 00:07:41,218 That makes total sense. 191 00:07:41,268 --> 00:07:44,868 it's a little bit, it reminds me of the initial iPad where those 192 00:07:44,868 --> 00:07:46,128 iPhone apps were running in like 193 00:07:46,143 --> 00:07:46,293 that 194 00:07:46,428 --> 00:07:47,538 that tiny window mode. 195 00:07:47,973 --> 00:07:48,423 Yes. 196 00:07:48,423 --> 00:07:48,568 There's 197 00:07:48,598 --> 00:07:49,108 Absolutely. 198 00:07:49,438 --> 00:07:50,133 Was it Instagram? 199 00:07:50,138 --> 00:07:53,188 Instagram doesn't do that anymore as of a few months ago, so thank you 200 00:07:53,203 --> 00:07:53,983 A Few months ago. 201 00:07:54,973 --> 00:07:56,413 they just released an iPad app. 202 00:07:57,113 --> 00:07:58,223 Yeah, future iPhones. 203 00:07:58,253 --> 00:07:58,943 What do you think? 204 00:07:59,573 --> 00:08:01,643 Is there something about this, it's oh yeah, this will work great. 205 00:08:01,823 --> 00:08:04,223 Foldable iPhones, or this will be like, 206 00:08:04,748 --> 00:08:05,858 that's an interesting question 207 00:08:05,873 --> 00:08:08,003 because I'm looking out for hints of that. 208 00:08:09,003 --> 00:08:09,483 I don't know. 209 00:08:09,483 --> 00:08:13,323 The iPad changes are very interesting because they feel like 210 00:08:13,323 --> 00:08:16,443 they had to take a lot of screen size considerations into account. 211 00:08:16,518 --> 00:08:17,148 an iPad mini 212 00:08:17,198 --> 00:08:17,888 oh my gosh. 213 00:08:18,008 --> 00:08:18,338 Yeah. 214 00:08:18,518 --> 00:08:22,778 No, a mini, from my understanding is just a scale down iPad. 215 00:08:22,778 --> 00:08:24,428 it's actually scaled down 216 00:08:24,428 --> 00:08:24,788 everything. 217 00:08:24,803 --> 00:08:25,433 everything looks the 218 00:08:25,433 --> 00:08:25,733 same 219 00:08:25,753 --> 00:08:25,913 Okay. 220 00:08:25,963 --> 00:08:30,743 I didn't see anything that stuck out to me, especially in terms of the UI hinting 221 00:08:30,743 --> 00:08:32,363 at New Hardware, but I could believe 222 00:08:32,363 --> 00:08:32,573 it. 223 00:08:33,113 --> 00:08:36,053 One of the things we talked about Peter and I on the last episode was 224 00:08:36,053 --> 00:08:40,493 like, are they trying to do something with this, the crease that's gonna be 225 00:08:40,493 --> 00:08:46,253 the inevitable problem with foldable iPhones, and is this glass design and 226 00:08:46,253 --> 00:08:49,793 the curve display and all this stuff, is that a way of them trying to address 227 00:08:49,793 --> 00:08:54,883 it in a way Dynamic Island Wood, or, the front display on the, vision Pro? 228 00:08:54,883 --> 00:08:57,493 They each address certain limitations of the hardware. 229 00:08:57,568 --> 00:08:57,808 Okay. 230 00:08:57,808 --> 00:09:01,018 This is a stretch, but imagine you have this phone that has a little 231 00:09:01,078 --> 00:09:04,138 bit of visual distortion, a display, sorry, that has a little bit of 232 00:09:04,138 --> 00:09:05,578 visual distortion right in the middle. 233 00:09:05,578 --> 00:09:05,608 Okay. 234 00:09:05,818 --> 00:09:06,418 treatments, right? 235 00:09:06,418 --> 00:09:10,258 potentially incorporate that deficiency into the user interface to make it look 236 00:09:10,308 --> 00:09:11,928 less like a mistake and more like a part, 237 00:09:11,928 --> 00:09:12,798 an intentional thing. 238 00:09:13,038 --> 00:09:16,218 Would it be like a book as opposed to a single display? 239 00:09:16,248 --> 00:09:16,968 Yeah, maybe like a 240 00:09:16,968 --> 00:09:17,238 book. 241 00:09:18,378 --> 00:09:19,398 There you go, apple. 242 00:09:21,138 --> 00:09:22,338 You got it, you got the idea. 243 00:09:22,338 --> 00:09:23,808 Now go with it. 244 00:09:24,118 --> 00:09:24,688 I like that. 245 00:09:24,748 --> 00:09:25,618 I like that a lot. 246 00:09:25,858 --> 00:09:26,773 I think that's pretty good. 247 00:09:27,763 --> 00:09:28,873 Anything else about the design? 248 00:09:28,873 --> 00:09:30,933 I think we've talked about it in the earlier piece, Anything 249 00:09:30,933 --> 00:09:31,953 else you wanna cover with it? 250 00:09:32,643 --> 00:09:34,563 I don't have a lot until I actually try it out. 251 00:09:34,563 --> 00:09:37,233 I'm very interested in how it looks on the Mac in particular. 252 00:09:37,623 --> 00:09:41,853 I like very minimalistic interfaces in general and it looked to me, from what 253 00:09:41,853 --> 00:09:45,333 Xcode certainly seems like it adopted this new stuff and it was a much more minimal 254 00:09:45,333 --> 00:09:48,213 looking interface, but it's hard to get a feel for it until you try it yourself. 255 00:09:48,408 --> 00:09:50,778 So good segue, let's talk about Xcode. 256 00:09:50,783 --> 00:09:53,523 Did you see the thing that everybody loves about the new Xcode? 257 00:09:53,578 --> 00:09:54,478 What was the thing everybody 258 00:09:54,478 --> 00:09:54,808 loved? 259 00:09:55,993 --> 00:09:56,263 settings. 260 00:09:56,338 --> 00:09:59,158 because they adopted the same settings, layout as system 261 00:09:59,158 --> 00:09:59,848 settings. 262 00:09:59,968 --> 00:10:01,108 I did notice this. 263 00:10:01,978 --> 00:10:02,848 How do you feel about that? 264 00:10:02,948 --> 00:10:07,328 Xcode has less settings than the system, so I think it could potentially work well. 265 00:10:07,328 --> 00:10:08,108 What do you think about it. 266 00:10:09,608 --> 00:10:14,868 I. I don't hate system settings as much as most people, but I sympathize 267 00:10:14,868 --> 00:10:16,158 with folks who don't like it. 268 00:10:16,848 --> 00:10:19,848 Having said that, I usually can find what I'm looking for because there's a 269 00:10:19,848 --> 00:10:22,248 spotlight search function at the top. 270 00:10:22,278 --> 00:10:22,818 Yes. 271 00:10:22,908 --> 00:10:24,048 That'll take me where I want to go. 272 00:10:24,048 --> 00:10:26,838 separate things you don't like that people usually don't like about settings. 273 00:10:26,848 --> 00:10:27,148 Yes. 274 00:10:27,148 --> 00:10:27,393 The actual setting. 275 00:10:27,423 --> 00:10:28,293 the search works well. 276 00:10:28,543 --> 00:10:29,353 the toggles 277 00:10:29,403 --> 00:10:31,293 They're just, they have a lot of strange behaviors. 278 00:10:31,343 --> 00:10:34,373 So I guess X code could bring that along too, but I bet you it doesn't. 279 00:10:34,743 --> 00:10:36,783 So let's get into Xcode. 280 00:10:36,813 --> 00:10:40,043 Xcode has, we can now hook up into LLM models. 281 00:10:40,073 --> 00:10:41,153 Huge focus on that. 282 00:10:41,393 --> 00:10:45,023 There's this new, one thing I wrote down was a new playground macro, which 283 00:10:45,023 --> 00:10:46,763 might make it easier to do quickly. 284 00:10:46,763 --> 00:10:49,703 Test code, very interesting play around and playgrounds is like 285 00:10:49,703 --> 00:10:53,483 specifically mentioned as a great use case to play around with alls, which 286 00:10:53,483 --> 00:10:56,573 I find really fascinating and I'm looking forward to trying that out. 287 00:10:57,323 --> 00:11:01,553 I don't know about how fixing code, especially Matt, for you fixing code 288 00:11:01,553 --> 00:11:06,053 that is not concurrency set up correctly if the LMS are gonna do a great job 289 00:11:06,103 --> 00:11:09,913 So when they showed this UI, it reminded me a lot of the rename feature, 290 00:11:10,063 --> 00:11:13,363 Concept, but I have had very poor luck with this working 291 00:11:13,363 --> 00:11:13,603 correctly. 292 00:11:13,653 --> 00:11:17,943 Now that's a little different because that is intended to be a precision tool 293 00:11:17,943 --> 00:11:19,953 that works 100% correctly or not at 294 00:11:19,983 --> 00:11:20,073 And 295 00:11:20,073 --> 00:11:20,223 that's 296 00:11:20,273 --> 00:11:21,263 This is not that way. 297 00:11:21,323 --> 00:11:23,963 So it might not be subject to the same problems, but it certainly 298 00:11:24,173 --> 00:11:25,973 made me hesitate when I saw it. 299 00:11:26,023 --> 00:11:26,953 Not until we try it out. 300 00:11:27,003 --> 00:11:27,393 Yeah. 301 00:11:27,393 --> 00:11:27,843 I don't know. 302 00:11:27,883 --> 00:11:29,113 There was such a big focus on that. 303 00:11:29,113 --> 00:11:30,703 I was interested in the UI changes. 304 00:11:30,703 --> 00:11:33,043 That was definitely something I wanted to check out. 305 00:11:33,208 --> 00:11:33,418 Yeah. 306 00:11:33,593 --> 00:11:36,623 There was a big focus on the LLM integration. 307 00:11:37,493 --> 00:11:38,603 People seemed excited about 308 00:11:38,603 --> 00:11:38,783 It 309 00:11:39,068 --> 00:11:39,398 Yeah. 310 00:11:40,088 --> 00:11:41,948 By the way, I finally figured out how to get. 311 00:11:42,623 --> 00:11:46,063 The Mac OS 26, VM to work. 312 00:11:46,153 --> 00:11:49,443 It gives you an installation error in bushel if you have to install 313 00:11:49,443 --> 00:11:53,493 X code 26 to get the VM to work. 314 00:11:53,613 --> 00:11:54,243 Interesting. 315 00:11:54,453 --> 00:11:55,173 that's possible. 316 00:11:55,203 --> 00:11:57,753 There's all kinds of things that I'm sure are broken or incorrect 317 00:11:57,753 --> 00:11:59,343 in the first betas that will. 318 00:12:01,863 --> 00:12:03,513 You shouldn't put it on your primary phone. 319 00:12:03,623 --> 00:12:03,803 Yeah. 320 00:12:03,853 --> 00:12:06,193 It's almost worth letting my phone crash for that. 321 00:12:07,003 --> 00:12:10,603 Okay, let's talk about, so machine learning, was there anything in 322 00:12:10,603 --> 00:12:13,573 there that you were interested in? 323 00:12:14,818 --> 00:12:17,038 The impression that I got from them was that they really thought 324 00:12:17,038 --> 00:12:20,518 about what people are looking for out of these tools and ways to give 325 00:12:20,518 --> 00:12:22,918 them, really easy to integrate. 326 00:12:23,293 --> 00:12:24,163 Systems into their 327 00:12:24,163 --> 00:12:24,433 code 328 00:12:25,093 --> 00:12:28,213 and that whole thing there was like all, it looks like it was macro 329 00:12:28,333 --> 00:12:32,173 supported or something along those lines to be able to define very like 330 00:12:32,203 --> 00:12:35,773 they're using actual swift types that you can put in and get out again. 331 00:12:35,823 --> 00:12:38,103 And I think that will be very appreciated by many people. 332 00:12:38,103 --> 00:12:42,383 There's this like generative macro that I saw, which sounds really interesting. 333 00:12:43,013 --> 00:12:46,763 Not only have they been emphasizing the use of app intense in our apps, 334 00:12:46,853 --> 00:12:51,023 but they've made it easier I feel like this year to do that as well. 335 00:12:51,203 --> 00:12:54,583 And it definitely feels like guys really get on the page, 336 00:12:54,643 --> 00:12:57,913 like start getting app intense so that your stuff is discoverable. 337 00:12:58,088 --> 00:12:58,778 I didn't, and especially 338 00:12:58,883 --> 00:13:00,623 the big emphasis on the new spotlight. 339 00:13:00,938 --> 00:13:01,928 So this is a macros thing, 340 00:13:01,978 --> 00:13:04,228 I think that might have been true on the phone as well, 341 00:13:04,258 --> 00:13:04,558 right? 342 00:13:04,558 --> 00:13:04,918 Sorry. 343 00:13:04,978 --> 00:13:05,938 That is true on the phone. 344 00:13:05,998 --> 00:13:06,568 Yeah, you're right. 345 00:13:06,998 --> 00:13:11,158 But it seems yeah, like they're making it easier and they're trying to continue 346 00:13:11,158 --> 00:13:15,158 to emphasize the use of, app intense and generative and that kind of stuff. 347 00:13:15,778 --> 00:13:16,498 And shortcuts. 348 00:13:16,558 --> 00:13:17,218 Shortcuts too. 349 00:13:17,218 --> 00:13:22,388 Looks amazing what you can do on Mac Os, with app intents and shortcuts 350 00:13:22,478 --> 00:13:24,758 and the Mach machine learning type stuff you can do in there. 351 00:13:24,758 --> 00:13:26,138 So I'm excited to try that out. 352 00:13:27,353 --> 00:13:27,983 Absolutely. 353 00:13:28,073 --> 00:13:30,263 I haven't played enough with Appin intents to have a really good 354 00:13:30,263 --> 00:13:32,568 opinion on this, but if you're excited, then I'm excited about it, 355 00:13:32,718 --> 00:13:35,238 I don't have a use case off the top of my head. 356 00:13:35,838 --> 00:13:38,708 I will have a use case, I'm sure once I've done app intense before 357 00:13:38,708 --> 00:13:41,108 and it's absolutely fascinating what you could do with it, but there's 358 00:13:41,108 --> 00:13:43,673 just so much potential and I think that's what I'm excited about. 359 00:13:44,673 --> 00:13:47,513 I. wanna skip the swift stuff because that'll be the stuff 360 00:13:47,513 --> 00:13:48,923 we'll really deep dive into. 361 00:13:49,013 --> 00:13:49,223 Sure. 362 00:13:49,323 --> 00:13:51,663 So we got 3D charts, which looked really cool. 363 00:13:51,663 --> 00:13:55,743 You can do 3D graphing, idle prefetch for better lists. 364 00:13:56,238 --> 00:13:56,508 Oh yeah. 365 00:13:56,508 --> 00:13:57,798 they really focused on that. 366 00:13:57,858 --> 00:13:58,878 Yeah, that was interesting. 367 00:13:58,978 --> 00:14:00,598 Specifically Mac os 368 00:14:00,713 --> 00:14:04,313 I think it's received a lot of criticism because I have certainly spent time 369 00:14:04,313 --> 00:14:05,753 working on list performance on the 370 00:14:05,753 --> 00:14:06,173 Mac. 371 00:14:06,513 --> 00:14:09,747 it isn't necessarily a straightforward thing, so I think it's received a 372 00:14:09,747 --> 00:14:11,217 lot of criticism and that's why I, 373 00:14:11,592 --> 00:14:15,732 is it just not do very well, or is it hard to play around with or what, 374 00:14:15,972 --> 00:14:22,242 because to me, like the list challenge was always because iOS devices are, 375 00:14:22,812 --> 00:14:27,222 they're just constrained on memory by far compared to Mac os. 376 00:14:27,222 --> 00:14:29,412 So I always thought Mac OS wasn't a big deal. 377 00:14:29,412 --> 00:14:31,002 Am I totally incorrect in that? 378 00:14:31,002 --> 00:14:31,512 No, 379 00:14:31,657 --> 00:14:34,627 no, you're right that the Mac has access to more memory in general, but I don't 380 00:14:34,627 --> 00:14:36,217 think that's typically the problem. 381 00:14:36,262 --> 00:14:36,562 Okay. 382 00:14:37,157 --> 00:14:41,387 And I think that in comparison to iOS, for example, which I have done 383 00:14:41,387 --> 00:14:44,297 the last work on, but in the Mac, there's many performance pitfalls. 384 00:14:44,347 --> 00:14:44,677 Okay. 385 00:14:45,607 --> 00:14:46,297 That's good to know. 386 00:14:46,577 --> 00:14:47,477 I don't do gaming. 387 00:14:47,542 --> 00:14:47,872 Yeah. 388 00:14:47,872 --> 00:14:49,822 I don't think that many people will either, 389 00:14:50,002 --> 00:14:53,992 Have they done less game demos now that they prerecord 390 00:14:53,992 --> 00:14:54,352 this? 391 00:14:54,452 --> 00:14:55,292 That's an interesting question. 392 00:14:55,302 --> 00:14:59,462 do, Cyberpunk, they did that and they did some other game, but it was pretty brief. 393 00:14:59,547 --> 00:15:03,297 they have done too much of an emphasis on demos and not enough of an emphasis 394 00:15:03,297 --> 00:15:06,537 on, here are the things we are building that are nice for game developers. 395 00:15:06,627 --> 00:15:08,577 It's a developer conference and I like to focus on that. 396 00:15:08,672 --> 00:15:10,352 I think they felt, you know what it is. 397 00:15:11,042 --> 00:15:13,662 Switch two came out last week and they're like, yeah, we shouldn't 398 00:15:13,662 --> 00:15:15,642 try to like one up Nintendo Uhhuh. 399 00:15:15,692 --> 00:15:17,312 So let's keep it, let's keep it slim. 400 00:15:17,732 --> 00:15:20,222 But yeah, they did do a lot as far as game development was concerned. 401 00:15:20,222 --> 00:15:24,872 The new gaming stuff does sound if I was a gamer or game developer, it 402 00:15:24,872 --> 00:15:26,762 does sound cool, what you could do. 403 00:15:26,792 --> 00:15:28,532 So we'll see how that goes. 404 00:15:29,702 --> 00:15:31,772 Vision os we have better anchoring. 405 00:15:31,922 --> 00:15:34,052 I'm really, we're not, we have to go to the other room 406 00:15:34,052 --> 00:15:34,922 if we wanna talk about that. 407 00:15:35,022 --> 00:15:38,202 But, yeah, vision os it definitely seems like they're still building stuff 408 00:15:38,202 --> 00:15:39,972 for it, so we'll see how that goes. 409 00:15:40,902 --> 00:15:41,262 Alright. 410 00:15:41,262 --> 00:15:41,802 Let's get into 411 00:15:41,807 --> 00:15:45,207 but if I'm not wrong though, there wasn't a major focus on a new version of 412 00:15:45,207 --> 00:15:47,207 Vision Os it seemed like minor changes. 413 00:15:48,077 --> 00:15:49,037 Is that your impression? 414 00:15:49,372 --> 00:15:52,822 I don't know because I haven't done any vision, Wes. 415 00:15:52,822 --> 00:15:52,852 Okay. 416 00:15:52,902 --> 00:15:55,422 it didn't feel like there's any major changes that are coming. 417 00:15:55,452 --> 00:15:55,692 Yeah. 418 00:15:55,742 --> 00:15:59,102 So swift big changes. 419 00:15:59,292 --> 00:16:01,962 We see continuing maturity of concurrency. 420 00:16:02,082 --> 00:16:02,532 Oh yeah. 421 00:16:02,892 --> 00:16:04,452 And yeah. 422 00:16:04,502 --> 00:16:10,352 What's your thoughts on where Swift 6.2 is as far as concurrency is concerned? 423 00:16:10,402 --> 00:16:13,102 If you go back to last year, so 6.0. 424 00:16:14,077 --> 00:16:18,997 I was convinced that the team was gonna release 6.0 and at the same time, 425 00:16:18,997 --> 00:16:23,197 they were also going to do all the work to at the very least have correct 426 00:16:23,197 --> 00:16:25,297 annotations for all of Apple's own SDKs. 427 00:16:25,297 --> 00:16:26,197 This was my assumption. 428 00:16:26,297 --> 00:16:27,137 And that did not happen. 429 00:16:27,237 --> 00:16:30,957 6.0 was a very big release and it came with it quite a lot of bugs. 430 00:16:31,617 --> 00:16:34,797 So then we have 6.1, which came afterwards, and that fixed 431 00:16:34,797 --> 00:16:35,967 a tremendous amount of bugs. 432 00:16:35,967 --> 00:16:39,207 And actually also along that way there have been a number of Excode releases. 433 00:16:39,207 --> 00:16:44,187 Those have also begun to iteratively include more annotations in the SDK. 434 00:16:44,247 --> 00:16:45,327 Very welcome stuff. 435 00:16:45,377 --> 00:16:48,857 brings along some major changes, but major not in terms of the 436 00:16:48,857 --> 00:16:50,177 language functioning differently. 437 00:16:50,177 --> 00:16:54,107 It does in a few ways, but mostly it's major changes to give you 438 00:16:54,107 --> 00:16:57,917 tools to be able to ease migration into this new language mode. 439 00:16:58,097 --> 00:17:00,407 What I haven't been able to figure out, and it doesn't seem like 440 00:17:00,407 --> 00:17:04,677 anybody has talked about anything, is changes to annotations for SDKs. 441 00:17:04,677 --> 00:17:07,947 Like one thing I looked at, for example, a library that I have had very little 442 00:17:07,947 --> 00:17:12,417 experience using, but a lot of experience helping people with is AV foundation. 443 00:17:13,167 --> 00:17:13,437 Okay. 444 00:17:13,437 --> 00:17:15,507 AV foundation is quite hard to use with concurrency. 445 00:17:15,507 --> 00:17:19,527 It's just, it's very dispatch focused and is missing a lot of annotations, for 446 00:17:19,557 --> 00:17:19,707 Okay. 447 00:17:20,397 --> 00:17:20,697 And as 448 00:17:20,697 --> 00:17:24,867 so far, there are a lot of new things in it, but I don't think there's anything 449 00:17:24,867 --> 00:17:26,607 related to concurrency that has changed. 450 00:17:26,697 --> 00:17:29,757 I looked at virtualization and yeah, it doesn't look like. 451 00:17:30,222 --> 00:17:31,812 now, it's still that beta one. 452 00:17:31,812 --> 00:17:33,312 So there still is room for these things to 453 00:17:33,312 --> 00:17:33,582 change, 454 00:17:34,007 --> 00:17:34,907 let's you know what happens. 455 00:17:34,907 --> 00:17:35,177 happens. 456 00:17:35,177 --> 00:17:35,179 It happens. 457 00:17:35,232 --> 00:17:35,662 Okay. 458 00:17:35,662 --> 00:17:35,872 If you 459 00:17:35,902 --> 00:17:38,482 there's, there is still, I don't think there's zero hope. 460 00:17:39,462 --> 00:17:42,332 But I was a little bit disappointed that there wasn't more emphasis there. 461 00:17:42,387 --> 00:17:42,717 Yeah. 462 00:17:43,017 --> 00:17:46,707 However, I will say there was an important compiler change that deemphasizes the 463 00:17:46,707 --> 00:17:48,717 need for some of these annotations 464 00:17:49,437 --> 00:17:50,007 You wanna go? 465 00:17:50,057 --> 00:17:53,597 No, so specifically they changed the rules around importing objective C 466 00:17:53,597 --> 00:17:53,897 code. 467 00:17:54,257 --> 00:17:55,097 Okay, go ahead. 468 00:17:55,097 --> 00:17:55,187 When 469 00:17:55,247 --> 00:17:56,387 import objective C code. 470 00:17:56,447 --> 00:17:56,687 Yeah. 471 00:17:57,182 --> 00:17:58,982 I'm all ready to do this 'cause it's part of my talk. 472 00:17:58,982 --> 00:18:01,712 When you import objective C code, if you look at a function, 473 00:18:01,812 --> 00:18:05,462 parameter, for example, the compiler assumes that it's escaping. 474 00:18:05,882 --> 00:18:06,122 Okay? 475 00:18:06,122 --> 00:18:09,392 And then you can tell it in objective C Oh, actually this is a non escaping thing. 476 00:18:09,392 --> 00:18:10,992 So that's a very conservative assumption that it 477 00:18:10,992 --> 00:18:11,382 makes. 478 00:18:11,442 --> 00:18:13,152 so the, okay 479 00:18:13,437 --> 00:18:14,277 You follow what I'm saying? 480 00:18:14,757 --> 00:18:15,387 It looks at, so you 481 00:18:15,447 --> 00:18:16,197 a keyword? 482 00:18:16,387 --> 00:18:17,527 You have to add these annotations. 483 00:18:17,527 --> 00:18:19,567 'cause objective seed doesn't need this information at all. 484 00:18:19,567 --> 00:18:20,227 This is only for 485 00:18:20,282 --> 00:18:21,872 it, it assumes the worst case. 486 00:18:21,922 --> 00:18:24,842 And then you put this special annotation to say, actually not escaping. 487 00:18:24,877 --> 00:18:25,147 Okay. 488 00:18:25,712 --> 00:18:29,312 But for sendible, which is much more important and more 489 00:18:29,312 --> 00:18:30,932 consequential if you get it wrong. 490 00:18:31,302 --> 00:18:33,222 It assumes non sendible. 491 00:18:33,282 --> 00:18:33,312 Okay. 492 00:18:33,572 --> 00:18:38,222 Which is, it makes it easier in some cases to use, but if it's wrong, the 493 00:18:38,222 --> 00:18:39,872 consequences are really terrible. 494 00:18:39,922 --> 00:18:43,882 So now if it can determine this is a completion handler, it will assume 495 00:18:43,882 --> 00:18:47,842 sendible, which will result in more warnings, but also it's way more safer. 496 00:18:47,842 --> 00:18:49,012 It's a much more conservative 497 00:18:49,022 --> 00:18:49,322 Okay. 498 00:18:49,502 --> 00:18:50,162 And I like this 499 00:18:50,162 --> 00:18:50,492 Yeah. 500 00:18:50,492 --> 00:18:51,512 That sounds really cool. 501 00:18:51,672 --> 00:18:53,112 This will actually help with AV foundation. 502 00:18:53,112 --> 00:18:54,942 I was just complaining about it, but it will make things better. 503 00:18:55,162 --> 00:18:55,492 Okay. 504 00:18:56,812 --> 00:19:00,152 Yeah, it's really great that they've continued to make 505 00:19:00,602 --> 00:19:03,182 objective C friendlier for Swift. 506 00:19:03,882 --> 00:19:06,402 just annotating the code with more information. 507 00:19:06,427 --> 00:19:07,777 It's not enforced, but 508 00:19:07,997 --> 00:19:10,817 I don't actually think this kind of stuff, I don't think the objective 509 00:19:10,817 --> 00:19:12,647 c compiler makes use of this at all. 510 00:19:12,652 --> 00:19:13,222 Exactly. 511 00:19:13,222 --> 00:19:15,292 It's like it doesn't care, but Swift will. 512 00:19:15,382 --> 00:19:15,622 Yep. 513 00:19:16,222 --> 00:19:17,482 The one thing I want to talk about. 514 00:19:17,482 --> 00:19:23,082 So we finally have, what's basically, static sized 515 00:19:23,427 --> 00:19:23,937 Oh, yes. 516 00:19:23,947 --> 00:19:28,927 my understanding was this was useful in the embedded space, but it sounds 517 00:19:28,927 --> 00:19:31,807 like it's also gonna be pretty useful, in the server side space 518 00:19:31,807 --> 00:19:34,507 as well and in a few other places. 519 00:19:34,687 --> 00:19:38,047 My guess would be that it's useful in any context where you're 520 00:19:38,047 --> 00:19:40,967 dealing with known fixed size data. 521 00:19:41,072 --> 00:19:42,182 I think it will be a performance. 522 00:19:42,242 --> 00:19:45,242 How much of a performance win it is, depends on the situation, 523 00:19:45,242 --> 00:19:46,852 Why didn't they have this in the first place? 524 00:19:47,627 --> 00:19:49,427 I don't have a good answer for that. 525 00:19:49,512 --> 00:19:52,662 my understanding is that there were some changes, like this ability 526 00:19:52,662 --> 00:19:54,642 to put an integer as a generic 527 00:19:54,672 --> 00:19:55,452 That is crazy. 528 00:19:55,452 --> 00:19:55,842 That looks 529 00:19:56,262 --> 00:19:59,622 They probably had to, and I don't really know how that works exactly, but I suspect 530 00:19:59,682 --> 00:20:02,512 that had a lot, there was a lot of type system work, and you can see this kind of 531 00:20:02,512 --> 00:20:06,352 trend happens a lot in Swift where they have some end goal that's quite far away. 532 00:20:06,632 --> 00:20:11,162 And they make a lot of changes along the way to be able to finally implement that 533 00:20:11,162 --> 00:20:12,872 And I think this is one of those examples 534 00:20:12,992 --> 00:20:13,862 DS sells for. 535 00:20:14,327 --> 00:20:17,537 Swift ui, like they had to do a lot of things to get to that point. 536 00:20:17,587 --> 00:20:17,647 ui, 537 00:20:17,742 --> 00:20:19,182 Now, what is the difference? 538 00:20:19,302 --> 00:20:24,582 So what is the difference between span an unsafe pointer and how 539 00:20:24,582 --> 00:20:26,562 does this affect objective C code? 540 00:20:26,707 --> 00:20:29,287 I wish I had a good answer for you, but unfortunately I 541 00:20:29,287 --> 00:20:30,697 have been ignoring that area. 542 00:20:30,712 --> 00:20:33,532 But you can get the right idea, even just by looking at the example that was 543 00:20:33,532 --> 00:20:35,152 presented during the State of the Union. 544 00:20:35,232 --> 00:20:38,892 they have, there are many existing SWIFT APIs for interacting with pointers and 545 00:20:38,892 --> 00:20:41,082 interacting with buffers of values. 546 00:20:41,262 --> 00:20:43,437 And they're pretty unwieldy and it can be quite difficult to get 547 00:20:43,532 --> 00:20:43,742 Right. 548 00:20:43,792 --> 00:20:44,962 variations, like subtle 549 00:20:44,962 --> 00:20:45,802 variations, 550 00:20:45,852 --> 00:20:49,302 and I think this is just another way to provide a mechanism where the 551 00:20:49,302 --> 00:20:53,352 compiler and type system can understand the underlying data so that they can 552 00:20:53,352 --> 00:20:58,762 provide a safer API, but also it looked like a much, more concise API as well. 553 00:20:58,862 --> 00:21:03,152 One of the things about SWIFT in the early days was how all of a sudden 554 00:21:03,152 --> 00:21:04,322 we didn't have to deal with pointers. 555 00:21:04,402 --> 00:21:08,302 This looks like a, basically a friendlier way to do pointers, especially since now, 556 00:21:08,302 --> 00:21:12,502 since there's interrupt with c plus and a few other languages that use pointers. 557 00:21:13,192 --> 00:21:15,202 This is what it seems like it's intended 558 00:21:15,562 --> 00:21:17,902 Yeah, I, now that you're saying this, I'm interested too, because 559 00:21:17,902 --> 00:21:22,072 there are many objective C APIs that actually use pointers as well. 560 00:21:22,122 --> 00:21:26,562 And I'm curious if they have incorporated the SPAN stuff or fixed size arrays 561 00:21:26,562 --> 00:21:28,842 into any of their own, like bridged 562 00:21:29,397 --> 00:21:30,357 I predict no, 563 00:21:30,547 --> 00:21:31,897 happens based on previous results. 564 00:21:31,897 --> 00:21:33,187 Yes, that's what I'm seeing. 565 00:21:33,847 --> 00:21:37,237 a number of years ago there was this system introduced called Extension Kit. 566 00:21:37,687 --> 00:21:39,097 Yes, it was introduced on the Mac. 567 00:21:39,097 --> 00:21:39,757 You talked about it. 568 00:21:39,817 --> 00:21:40,177 I really? 569 00:21:40,177 --> 00:21:40,357 Okay. 570 00:21:40,357 --> 00:21:40,567 Yeah. 571 00:21:41,312 --> 00:21:44,442 So it was introduced for the Mac and then, maybe bits and pieces 572 00:21:44,442 --> 00:21:46,812 were a little bit available in iOS, but it was non-functional. 573 00:21:46,962 --> 00:21:52,932 Then the next year of big portions were introduced for iOS, but not the core bit. 574 00:21:52,932 --> 00:21:56,622 You need to actually make it work, which is very suspicious. 575 00:21:56,622 --> 00:21:56,623 Yeah, 576 00:21:56,757 --> 00:21:57,297 that is really 577 00:21:57,402 --> 00:22:00,672 Yeah, and I just assumed, oh, something had gone wrong and I predicted the next 578 00:22:00,672 --> 00:22:02,442 year it would show up, which it did not. 579 00:22:02,442 --> 00:22:02,472 Okay. 580 00:22:02,697 --> 00:22:02,967 Okay. 581 00:22:02,967 --> 00:22:04,797 then the year after that, it also did not show up, 582 00:22:04,847 --> 00:22:05,267 It showed 583 00:22:05,372 --> 00:22:06,002 Yes, it did. 584 00:22:06,167 --> 00:22:07,007 That is awesome. 585 00:22:07,052 --> 00:22:09,782 I haven't actually played with it, but it certainly looks like it's functional. 586 00:22:10,007 --> 00:22:10,397 Okay. 587 00:22:10,647 --> 00:22:12,087 You'll have to come back and report that 588 00:22:12,137 --> 00:22:13,127 Yeah, I'm very interested 589 00:22:13,177 --> 00:22:13,507 Yeah. 590 00:22:14,347 --> 00:22:14,647 I think it's 591 00:22:14,647 --> 00:22:15,007 a lot. 592 00:22:15,017 --> 00:22:15,287 that's it. 593 00:22:15,337 --> 00:22:19,057 We'll be playing around with this and I will be reporting back. 594 00:22:19,087 --> 00:22:22,117 I'm sure we'll have some more guests on the show when I get back to Michigan. 595 00:22:22,737 --> 00:22:24,507 Thank you so much, Matt, for joining me for this. 596 00:22:24,557 --> 00:22:25,217 It was wonderful. 597 00:22:25,467 --> 00:22:26,637 Where could people find you online? 598 00:22:26,817 --> 00:22:28,857 you can find me@maico.org, 599 00:22:28,907 --> 00:22:32,027 And if you're looking for help with Swift 6.2 and concurrency, 600 00:22:32,027 --> 00:22:34,027 definitely check out his website. 601 00:22:34,057 --> 00:22:35,557 It's excellent source for that. 602 00:22:36,107 --> 00:22:37,277 Thank you so much for joining me. 603 00:22:37,377 --> 00:22:39,027 If you wanna try out Mac Os. 604 00:22:39,402 --> 00:22:41,892 26 and you don't wanna break your laptop. 605 00:22:42,052 --> 00:22:43,162 Definitely check out Bushel. 606 00:22:43,162 --> 00:22:43,972 It's on sale. 607 00:22:43,972 --> 00:22:44,992 Pro subscription. 608 00:22:45,502 --> 00:22:47,482 Make sure you install Xco 26 though. 609 00:22:47,482 --> 00:22:49,802 But you can definitely play around with it, there. 610 00:22:49,952 --> 00:22:54,122 Thank you so much for joining me for today's episode, and I will 611 00:22:54,122 --> 00:22:55,472 talk to you when I get back home. 612 00:22:55,532 --> 00:22:56,102 Bye everyone.