 It's Python and Harper time. Okay, this week, lady, I got a couple things. Yep. So CircuitPython8 is released. Yep. What should people know or do about CircuitPython? What's the big thing if they want to? The big push is expressive support and PicoW. It's now released. It's pretty stable. Tell us if there's any bugs you find. It does resize partitions for something. So if you've been using early release candidates or betas, check the notes as a warning. It tells you, hey, if you're using these boards, we resize the partitions. A lot of it is because we added so much stuff that we had to make more space for firmware. So just make a backup of the code that you have running on your CircuitPython device. If so, not a big deal, but it's ready for people to try out. We tend to do an eight, a one pretty quickly, because when we do a release candidate, people use them, but then when you actually release, release, that's when people start using them and it's the default. And so we're gonna get a lot more bug reports and so we'll fix those. And you'll see like an 801, 802 come out pretty quickly. But that said, please do update your boards. I've been using eight, it's been great. And we're on our way to nine, which will have some stuff like maybe USB host, maybe high speed chips, maybe more native display support. We'll see what's up. Yeah, we were talking about like, how do we do things like non-net connected machine learning as the chips get more powerful. So we have lots of roadmap plans, but everything's out in the open. You can actually even check out our CircuitPython 2023, some repos for some of the stuff that we wanna do. I'm still looking forward to like, having lots of video things. Yes. That's one of the things. Yeah, like art on screens. So the next thing, of course, you know, check out the newsletter. It's AdafruitGilly.com. It's a completely separate site. We do not harvest your emails, do anything that's why we made a separate site. We did not want it connected to your store experience in any way. But what I wanted to do this week was, we get asked all the time, why don't, why doesn't Adafruit have a board comparison guide with all your stuff? And the thing is there's, there's so many people that are, that's what they're doing. They're making comparison guides, like make does it. And then this one came out. This is from eitherway.io. And this is one of the ones that we got asked to do. And it's just like, I'm just going to point people there. So it's ESP32 buyer's guide, different chips for more sensors. And there's a couple of things that, I mean, you get asked this a lot. So I figured like, this could be like one, which are the best ones to run something like certain Python or MicroPython. But what are the things to look out for with like the differences with ESP8266, ESP32, ESP3. It gets confusing, especially with some of the names of these. So you saw this chart. What do you think of it? Well, I think, you know, it's a good overview. You know, I think that there's a couple of assumptions that they're making, which is that you're not necessarily using it with Python. And also, you know, they looked at technical specs and not necessarily what the SDK support is for them. So for example, they're like, oh, we recommend the C3. It's like, well, the C3 is really cheap, but it also doesn't have as much support and also doesn't have native USB. So they're like, you just go straight to the S3, but you know, we've seen some more bugs with the S3 that are still being worked out because it's quite new. I still like the S2. I think it's really good. The ESP8266 definitely don't use it anymore. Like really, it's not a good idea. If you absolutely need something that cheap, the C3 is a good alternative. But other than that, I'd say the ESP32 classic is still, you know, very popular, a lot of code support for it. After that, you know, the S2 is very good. S3 is kind of new, but I feel like it's getting more and more stable. And then the C3, which is really bare bones. So, you know, they didn't, it's not that they didn't pick these, but I have some different reasons. For me, it's not just hardware price. It's, am I seeing a stable IDF experience with it? Yeah. So if, because it is confusing, because, and I think a lot of folks are still, when they hear ESP, they're thinking of like the 82.6, like the first round. Yeah, yeah. Yeah, don't use the first and the 86.6. So that's basically the best suggestion that they had. Yeah. So if someone right now, oh, by the way, they have a neat comparison table. Let me go to this. So you can, it's on GitHub. So this just means like, I actually like that they did this because other people can contribute to it and other folks have forked it. And then there you can see the revisions. We do this with some of our stuff, like our, we did a circuit Python, micro Python thing on GitHub. We also did a, we have our awesome feather and we have a few other things. We have all awesome circuit Python. But I like this because this is going to change, change over time. But if someone was like, okay, I just want to have something that kind of does everything. I plug it in the USB, it works. I can run circuit Python on it. I can do, I can get started really fast, but then I can do some stuff. Which, which board should, do you think that is a good? The S2 is a good one. I think the S2, I mean like, I really feel like they're very stable. I mean, if you're absolutely beginner, beginner, you know, the ESP32, the original has just the most broadband support, but for the good experience, I think the ESP32 S2, like I mentioned, is the best family. All right. And I really appreciate they chose some of our boards for this and the QDPI, ESP32 C3, Wifi DevWord, and that for ESP32 S3 Feather. Check it out. Good, good, good guide for folks who want to choose. The other thing that's kind of nice is like, if we did a guide, we would probably like, well, here's our board. It's really hard to keep track of everyone else. It's not like it when someone else... It's independent for a party. Like, pay them. We didn't send them anything. They just, they just... Yeah, like if we did a guide of just like, which board to pick, I think it would be suspect. Like, well, we think our boards are really good. And we're like, well, of course you do. You're right for it. So anyways, so do check that out. And I think if you want to run Python on Hardware, this is a good place to start. And that is this week's Python on Hardware news. Don't forget, go to Advert Daily. Deliver to your inbox every single week. And special thanks to Ann, who does an amazing job. And then Ann sent a hug report. We do that for our weekly all company meeting to Dan who always proofreads. Thank you, Dan. All right.