 Python on hardware. Okay, this week, lots of news. I'm going to divide up the news in two sections. Straight-up newsletter stuff. So this is from the newsletter. I've already scrolled down because we're going to talk about some other stuff in a second. But Python 3.1.1, to be twice as fast as its predecessors. That's a big deal. Python's not slow, but it could be faster. Yeah. In October of 2022, but the plan is to have it quadrupled. But we'll see what's in there. So the presentation about all this is more is on GitHub. PSF, Python Software Foundation has a new executive director named Deb. Let me read about Deb and more. This was interesting. I'm going to caution y'all who are super Python fans. So IEEE spectrum, top programming languages for embedded Python. Python, could it be? Is it embedded? Yeah. So see the little chip? So it's web, it's computer. Oh, and embed. And embed. So Java is still being on mobile, C, mobile, C++. But I think these results are a little skewed, and I think it's our fault. Okay. Because there's a lot of people getting into programming on microcontrollers, and they're using circuit Python, they're using microPython, they're using Python on something like a Raspberry Pi. Yeah. And so I think that it's skewing that way, which is fine. I don't necessarily think that everyone who's doing embedded is doing Python yet, but I think we're getting closer and closer because so many people know Python that it translates really well to whatever you happen to be in front of. And batteries include it, so you get very far, very fast. And when people need to do things, like you were doing this HID mouse from 30 years ago, use Python to interact with it. It makes it real easy, makes it real easy. So it's interesting, like I said, I don't think that Python is number one. And they also classify Arduino as its own language on here, so that Arduino is number 11. Python zipped to the top at number one. I think obviously there's a lot of people using Arduino for embedded. So anyways, interesting stuff. Take a look at it. I can believe Spectrum is serious business, so that's kind of neat to see. We have all the news that you can expect in our newsletter every single week. This is kind of a neat, a portable severance aluminum terminal. I think Todd bought that one. It's kind of like the DVD logo. And all the projects that you know and love and get inspired by YouTube. There's some fun part. I like the little spinning black and white thing. What's it called? The Cooks Radiometer. Somebody made like a cyber one. There is a LinkedIn-class circuit Python connecting a robot cat to the internet. I mean, look at that cat. Yeah, and E-ink badges and more, but the news this week, a lot of it is circuit Python related, because we haven't got to talk about it. First up, thank you again everyone who joined the Discord, 34,000 people. This particular month happened faster or the time period to get there. This is what the Discord growth looks like all the way back from 2019. That's pretty linear. And not bad. And we also don't publish our server into the directory because it bots use it and spam and lots of drive buys. And so this is people who actually want to stop in and do things. Yeah, it's interesting. If you look, it looks like right when COVID hit, there was a big spike. It looks like it was about March, 2020, a lot of people joined. We also did a membership drive when we were in server discovery. We're just like, hey, everybody stop by, but it turns out that that wasn't great for all of our moderators and for all of us because there was just a lot of spam. And then on Reddit, we just hit 3,000 people on the circuit Python Reddit and go to reddit.com, slash r, slash circuit Python. And then we hit 350 libraries. And that's what we're talking about on Friday and deep dive. And here's a chart of how the libraries are going. Looking good. Nice graph. Yeah. And so I guess I wanted to ask you because we turned this little segment into a standalone thing. Why do you think there's so many circuit Python libraries? There's 350. So I wrote a lot. Yeah. But why do you think because we have more circuit Python libraries than Arduino libraries? Why did that happen? We actually have about the same number, but... Really? I thought it was a little bit more. I think we have about... Well, I mean, circuit Python we have contributions to. It's almost about the same. Okay, let's say it's about... Why did it catch up so fast? Yeah, why it catch up so fast? Which is a good question. One of the things when we designed circuit Python is we kind of came at it backwards. One of the things I wanted to make sure is that we had a lot of libraries. It was easy to write libraries. It was easy to support libraries because at the time, I was writing libraries for MicroPython as well as for Python on Raspberry Pi. And that was what was driving me nuts was like I had to support both because MicroPython was different enough from Python that the code wasn't compatible. And so we specifically designed circuit Python to make it so that code could run on a Raspberry Pi computer or a Raspberry Pi Pico now. And it would be the same code. You know, the pin numbers would change, but that's normal, like that always changes. But the functionality and the way the code was written and the libraries was written and supported would be the same. So what's great is that for every product we make now, we make sure to have a circuit Python library because it covers hundreds of single board computers because Raspberry Pi and all the Raspberry Pi likes as well as the 200 different, 250, 260 different circuit Python boards. And the universality of those libraries was really important. 295 boards. 390, almost 300. Almost 300 boards. There's a graphic coming, it's gonna be the three. It's like this, but 300. It's like three, but 300. And another thing is that we sell hardware and so I wanna make sure that people can use our hardware with circuit Python. And also, I wanted, you know, the final piece is that one of the things that people find annoying about circuit Python is they're like, why did we do the bus and GPIO libraries? Like why is it different than MicroPython? Why didn't you just use machine? And the answer was at the time there was actually wasn't a unified interface. There wasn't a unified way to make sure that a library would run on every MicroPython board. You know, later on machine was invented and PiB went away, but for a long time it was like every board had their own kind of slightly different way of defining stuff. And so having a universal bus library, a bus interface for circuit Python meant that we could write libraries and they would work on every board. And so far, other than a couple freaky exceptions with like I squared C and, you know, whether they have clock stretching support or not, pretty much every library will run on any circuit Python board. And that was a goal and I think we've done a really good job of it. And just from like a very high level thing, from, I think an observer would say, oh, you have, because you have lots of libraries, you have lots of boards, but because we have lots of boards, we have lots of libraries. Like it's really neat. No, we went to libraries first. The libraries came before the boards. It's really neat. And there's folks that have entire businesses based on the fact that they don't have to worry about the software for the hardware because every time there's a new version of circuit Python, it just works because there's universal support across 295 boards. And another, you know, 150 Linux boards. So anyways, big milestone. Thank you everyone who's been a contributor and everyone who's been watching this story. It is part of the newsletter delivered to you every single week. We don't spam or anything like that. You can go to AdafruitDaily.com and sign up. All right.