example. I have um I have an M3 Ultra right here that I'm using has 512 gigs of RAM and I'm able to run Deep Seek R1. Uh, granted it's the four-bit quantization, but I can run that entire 671 billion parameter model locally on the Mac, which is insane, right? I mean, you would need like I won't do the math in my head, but you'd need a lot of 590s and 4090s, you know, uh, with, you know, a few thousand watts of power consumption to do that. And this thing's sitting over here as I'm looking drawing a couple hundred watts, you know, just, uh, in normal usage. So yeah, it was funny because we had like we had the move, you know, Apple's done a move in terms of processor architecture multiple times, right? It's how we got this fat binary as it were, universal binary and like there was this awesome time for just a short period where we didn't have that. Everything was just Intel and Intel 64-bit and we didn't have to worry about any changes and then all of a sudden they introduce silicon, right? and we're running ARM and we're back to the universal binaries where everything's twice the size that it used to be and like to me that was kind of like ah but then you see the benefit you get from it once you get that ARM processor like running and yeah it's fantastic I would agree with that as well. Yeah. Speaking of which I heard that Mac OS 26 is supposedly the final version to support Intel uh based Macs. I think Apple had officially announced that. So that's uh that's going to be interesting. That means Mac OS 27 will theoretically be Apple Silicon only. So yes, I believe I heard that as well. Although I thought it was Oh, yeah. Yeah, that might be right. I couldn't remember if it was the release of 27 or if it was 2027. I can't even remember the the release now that they're calling it by year now, right? That that's what by year. Yep. They've changed the nomenclature, but uh yes, so it's uh it's coming though. So the death of Intelbased Macs is uh is well depending on your perspective fortunately or unfortunately coming uh before you know it. So I think it depends on when you bought your Mac. If you bought it year before Yeah. If you bought a uh $50,000 uh Intel powered Mac Pro, I uh Yeah, that's not a good place to be in. But all right. Well, um the main thing I wanted to ask you about here, uh for sure was your book, uh because um you know, I know that you have a new threat hunting book, uh that is coming out. I've pre-ordered it myself. And by the way, if you check this video's description, you'll find links to pre-order the book. Um as well as to the Mitt and Mack website and the things that we've been discussing here. But tell us a little bit about this book. what does it cover and what you know what was your uh I guess motivation for writing it and so on. Yeah, absolutely. I've always had an interest in kind of trying to share the knowledge, right? And I feel the uh I feel the Apple space is the right place for that because again it it's still it's at a point where we're starting to get a lot more attention from a security perspective on uh on Mac OS. Um, but it still remains fairly niche and it still remains like a lot of the, you know, big quote unquote sexy, if you will, attacks are still occurring on Windows. Windows has their server infrastructure, right? Macs are generally owned by a single individual. But like there was this time where somebody would get hit and nobody knew how to look at it. determine if an attacker was successful on the system. um and that's shifting a little bit, but there's still a lot of I find um desire for knowledge on how to find those threats um and determine what happened based on a number of events. Right? So, uh I do have a first book that I wrote that's uh that's called OSX, Incident Response Scripting and Analysis. As you can probably tell by that name, it's pretty old. That book was 2016, right? Uh and that was uh there was a lot of focus on that for more or less handling artifacts. Um a lot of stuff that you're covering, you know, in your training now. Um except you're doing it in a very more modern updated way. So uh but the original book I put out was about being hands-on, getting artifacts, and then parsing those artifacts to tell a story. uh and this uh this new book that I'm working on is more geared towards how do you do that uh with kind of uh from an EDR perspective, right? How do you take events that a system that many systems and security software sends up to the cloud in real time? Um how do you take those events and tell a story? Uh so uh a lot of that is through um process creation, right? Monitoring process creation. what are different processes, things like that. Um, file activity. How do you know when a certain file is modified? Take a look at the process that modified it. How do we look at the process heritage to determine if that's weird or not? Um, basically just trying to teach uh a lot of stuff that I've done over the past, you know, 10 years of my career. Uh, and trying to put that in what is hopefully a digestible manner. Um the ultimate goal is to teach uh Mac OS internals so that you can use that internals knowledge for your security benefit, right? Um and trying to find that line of internals versus security content can be pretty tricky like some people go heavy on one like the computer science side, some people go heavy on the other. But I think learning about threat hunting is finding that balance of both. Um, and that's what I'm trying to do with the book. Yeah. Excellent. I also noticed on