 OK, Python on hardware. I thought this week we'd go over a couple of things, Lady. The newsletter has so much stuff. And usually we pick one thing. This week we're just going to do a smattering. So if your swine user has a very pie, there's an update. It has the new Linux kernel. So that might be something. Fun term support. Yeah, that might be something that you want to do. It also has the latest update with Matlab. We try to use the newsletter for events that we know the people who read the newsletter. So Kikon, or Kikon, yeah. Either one is fine. But it'll be September 9th to 10th this year. So if you use the open source CAD tool, check it out. We're probably going to sponsor or do something in some way. There's a post about CircuitPython and version control. If you want to use some type of version control. Yeah, but you're still on the disk drive. It kind of manages the file movements for you. And then for folks who've been using Python with a block editor like edublocks and Kanda acquired edublocks. Being big news in the maker world, if you're into that. And then I thought I would spend a moment on this. And then I'll go through a couple other ones. But what's the best language for microcontrollers? Micpython, CircuitPython, or GNRC. I think, in general, these type of comparisons are bad. Because, and I'm going to say bad as far as it brings up the bad in people, because it gets very territorial. It's like, no, see or die. Weird engineerism, that it's like, they're going to be the best. And it's like, yeah. And some people will do a drive-by and just be like, Python and microcontrollers, dude, die. Well, look at 8 or 3 now. Yeah, rare. Yeah, pot smoker for baby language for pot smoker, which is what Arduino was called a long time ago. And I did that. I put that quote in my article. And the guy, Arne, didn't like that. So because apparently at the time, Arduino was it was too dumbed down for people. Well, do you think that's dumbed down? Yeah. Running a scripting lounge on my controller will, like, expose that. So here's what I would propose. Because I do like, I do think. Let's check on that guy. Ask who he thinks about circuit python. Not good. It's too easy. You're making it. It's too easy. So one of the things that I think that would be helpful and we can't do this because where Adafruit is, I do think it'd be neat to take a project and say, OK, we wanted to have a water sensor alert our phone when there was a flood in our basement. And then from the very beginning, just like, I didn't choose whatever hardware you want. Maybe everybody has to use ESP. Let's take a 50-button. ESP is ESP32 S2 because, you know, all everything is supported on that. You know, Arduino, you can use micro-python, circuit-python. And I think what would be better is how fast can you do it? How much fun can you have? How much time do you actually need to spend to do that project? Because I think that's one of the things that we should measure if what is better to use than something else. Not because the language is better. It's just because it's more suited. For instance, if you're going to do things where, like, you're getting strings of text on the internet, Python is probably better because it's faster because there are these batteries-included libraries. So I think that might be a subtle change instead of which is the best language is, like, what's the fastest way to get your project going? Because there's a lot of times where you want to have, like, oh, I just wanted to text my phone when my basement's flooding. That's it. That's all I want to do. And the best language isn't probably going to be the fastest language. Because best is subjective, but fastest, I think we can all agree. Some of them are faster than others as far as getting the project done. Not the speed, like, oh, how many milliseconds, but how long does it take you to get the project going? Like, there's certain bits of hardware, like Stemma, that makes things easier. There's certain things like Python libraries make things easier. So I think that would be a way to go. Another example is, like, so MakeCode could be in this list, because there's a lot of projects that are, like, if you just want, I just want to do some swirly things with LEDs really fast for a costume. MakeCode, almost instant. Is it the best language? Depending on who you ask, like, you know, there's internet jerks that are going to say, yeah, you know, you should use machine code, you know, somewhere, whatever. I don't understand why they use Twitter if that's the best language. Anyway, so I think that's just, you know, a slight different way of looking at these things. Anyways, you can check out the rest of the projects and more. I like this, like, universal computer thing. Oh, it's just cute. Yeah, you know, speaking of the E-Mate, this is kind of... E-Mate, too. This is what it reminded me of. Pymate. Yeah. And then someone in the chat just did Prime's Drag Race. I liked the idea of Drag Race. Maybe we'd say, like, like, Drag Race would be a term for you set out what the project is and then who can get the project in fastest and then you look at what they used. That'd be kind of cool. Anyway, so that's our Python on Hardware Newsletter this week. One other little reminder. Happy birthday, MicroPython. Turn 10. I'm now out to Damian. We're going to do a donation. We already do stuff with GitHub sponsorship. If you use MicroPython, send them a buck or two. It's what circuit Python's based on. We deliver this newsletter every single week on your inbox. AdvertDaily.com. We don't spam you. We don't do anything other than send you the email once a week.