Michael Kennedy: Hello and welcome to Python Bytes, where we deliver Python news and headlines directly to your earbuds.
Michael Kennedy: This is episode 458, recorded November 17th, 2025.
Michael Kennedy: I'm Michael Kennedy.
Michael Kennedy: And I'm Brian Okken.
Michael Kennedy: And this episode is brought to you by us.
Michael Kennedy: All the things that we're doing.
Michael Kennedy: We have many fun and useful things to offer you.
Michael Kennedy: pytest books, pytest courses, Python training courses,
Michael Kennedy: the agentic AI programming course about how you take agentic AI
Michael Kennedy: and turn it from like weird wizardry smushiness into engineering.
Michael Kennedy: It's going incredibly well.
Michael Kennedy: So check that course out.
Michael Kennedy: Follow us on the socials.
Michael Kennedy: Put them by set up slash live if you want to see this live
Michael Kennedy: or streaming live or see the old shows.
Michael Kennedy: And be sure to sign up to our newsletter.
Michael Kennedy: We have tons of people really getting a lot of value with that.
Michael Kennedy: Brian's putting that out.
Michael Kennedy: And yeah, it's truly nice.
Michael Kennedy: It's not just the links of the show notes,
Michael Kennedy: but it's extra deep information, background information,
Michael Kennedy: that kind of stuff.
Michael Kennedy: And the joke, always the joke, Brian.
Brian Okken: Always the joke.
Brian Okken: And we put a link to the joke, if we can find a link to the joke, in the newsletter as well.
Michael Kennedy: Exactly.
Michael Kennedy: Sometimes the joke has a link, and sometimes it's just like a dad programming joke, and it just has words.
Michael Kennedy: What do you want to talk about first?
Brian Okken: I actually want to talk about Django.
Brian Okken: Oh, really? Okay.
Brian Okken: And actually, kind of lightweight, I want to talk about the Django website.
Brian Okken: I guess I heard about this, but there was a discussion about maybe redesigning the Django
Brian Okken: website.
Brian Okken: It's been the same for a while.
Brian Okken: And it works.
Brian Okken: It's good.
Brian Okken: But I noticed Adam Hill put out a mock-up for what the Django website might look like.
Brian Okken: So here's his new one.
Brian Okken: And I'm kind of liking it.
Brian Okken: I like the animated thing at the top.
Brian Okken: It's the task framework.
Brian Okken: It's the web framework.
Michael Kennedy: Did Django just jump like 20 years into the future?
Michael Kennedy: Yeah, it looks...
Michael Kennedy: From where it was to the current day, it was.
Michael Kennedy: It looks pretty good.
Brian Okken: It's got like search documentation at the top
Brian Okken: that's really easy to find.
Brian Okken: I mean, I guess there was...
Brian Okken: Yeah, there's no...
Brian Okken: I don't know where you have to...
Brian Okken: The search documentation isn't at the top here.
Brian Okken: I like the search there.
Brian Okken: I'm liking it.
Brian Okken: I like just the life of it.
Brian Okken: Feels good.
Brian Okken: I think that maybe we should go with it.
Brian Okken: but you know it's just my vote but that you can you can join the discussion too if you'd like to
Brian Okken: help out and and there is some assistance that that adam hill is okay with so there's and
Brian Okken: it's not just him if you i'm putting a link to a discussion uh where he announced what his little
Brian Okken: his demo um he said i'd love help with in the form of prs to the repo explicitly not looking for
Brian Okken: drive-by critical feedback without PRs. It's fine. I guess here's my drive-by feedback. I like it.
Brian Okken: I know that's not really, but I do like it. And, but you can read, it looks like he kind of picked
Brian Okken: this up off of other, there was other work. Just a reminder that this doc informed my approach. So
Brian Okken: there's another document about things. I didn't look at it actually, but the discussion's been
Brian Okken: going on for a while, if I scroll to the top, there's been a discussion on, let me do this,
Brian Okken: up to September 21st. Oh, it looks like he started it, that maybe we ought to redesign the website.
Brian Okken: It's not too long, man, September 21st to now. But I think that it'd be cool to give. Why not?
Brian Okken: Let's go for it.
Michael Kennedy: You know what? I think, look, Django's a web framework. It should not look like it's, you know,
Michael Kennedy: 15 years old and outdated and rusty. I mean, it's a project that's getting tons of love and
Michael Kennedy: attention. And I think it's a really good idea to make it feel like it belongs at the cutting edge
Michael Kennedy: of web development these days. And, you know, just that website is aged. Yeah, it's like a long time,
Brian Okken: right? Yeah, it is a long time. But also, even if the it should be a the to make it feel alive,
Brian Okken: also the website could be in progress.
Brian Okken: It could change also.
Brian Okken: Not that, I mean, even if this one doesn't,
Brian Okken: I mean, maybe this is great
Brian Okken: and this will be great for,
Brian Okken: the new one will be great for a long time.
Brian Okken: But I think that we should be tweaking it
Brian Okken: on a regular basis
Brian Okken: just to make sure people understand
Brian Okken: that it's still moving.
Brian Okken: Yeah, absolutely.
Michael Kennedy: And hat tip to Adam Hill.
Michael Kennedy: That is a very nice looking website.
Brian Okken: Yeah, I think it's neat.
Brian Okken: Plus, I love that.
Brian Okken: I got to say,
Brian Okken: I love the documentation at the top,
Brian Okken: the search docs,
Brian Okken: because I often just go there,
Brian Okken: because I'm used to going to a project homepage
Brian Okken: to search the docs.
Brian Okken: So, yeah.
Brian Okken: Yeah.
Michael Kennedy: All right, what you got?
Michael Kennedy: I want to dive into some concurrent database stuff.
Michael Kennedy: So I want to talk about aiosqlitepool.
Michael Kennedy: So there's three concepts here.
Michael Kennedy: Async IO, SQLite,
Michael Kennedy: and then a connection pool type of thing.
Michael Kennedy: So normally you just work with SQLite
Michael Kennedy: And it just says, hey, let's go open up all the infrastructure to talk to the SQLite database and do your work.
Michael Kennedy: And then it closes it.
Michael Kennedy: Then it opens it.
Michael Kennedy: Then it closes it.
Michael Kennedy: Then it opens it.
Michael Kennedy: And that's not necessarily the fastest way to do that.
Michael Kennedy: Maybe you could just leave it open.
Michael Kennedy: But you don't want to leak these connections or have a whole insane ton of them open.
Michael Kennedy: So instead, the idea is to use this connection pool.
Michael Kennedy: So you say, instead of giving me a connection, you say, give me a connection from the pool.
Michael Kennedy: Right.
Michael Kennedy: And it'll keep a certain number of them open and hand them over to you when it needs or wait.
Michael Kennedy: If there's already 10 connections running queries, you probably can just better off to wait and try to hit it with another.
Michael Kennedy: So that's what this is.
Michael Kennedy: And it's not a replacement.
Michael Kennedy: Maybe people have heard of AIO SQLite.
Michael Kennedy: AIO SQLite is a way to talk async and await, but to SQLite.
Michael Kennedy: And all this is a little bit funky and interesting because SQLite is a file that runs in process.
Michael Kennedy: It's stored as a file and it's a thing that runs in your Python process.
Michael Kennedy: So you're not going out to the network and waiting and that kind of thing.
Michael Kennedy: But this AIO SQLite gives you an async programming model.
Michael Kennedy: But the way it works is you create a connection, do a query,
Michael Kennedy: and then when you do async with, when that with block,
Michael Kennedy: that context manager closes, the connection's gone.
Michael Kennedy: So over and over, it's kind of up and down.
Michael Kennedy: And so the idea is this aiosqlitepool wraps this SQLite library
Michael Kennedy: for basically three core problems.
Michael Kennedy: One, it tries to eliminate connection overhead
Michael Kennedy: by avoiding repeatedly opening and closing
Michael Kennedy: syscalls, mem allocation, teardowns,
Michael Kennedy: all that kind of stuff, right?
Michael Kennedy: Which I already described.
Michael Kennedy: It also has the advantage of potentially faster queries
Michael Kennedy: via hot cache.
Michael Kennedy: So long-lived connections keep SQLite's
Michael Kennedy: in-memory page cache hot, right?
Michael Kennedy: So once a database has seen a query,
Michael Kennedy: it has to look at the query and say,
Michael Kennedy: okay, we're going to come up with a query plan.
Michael Kennedy: Do we use this index?
Michael Kennedy: Are there any indexes?
Michael Kennedy: How are we going to sort it?
Michael Kennedy: Is it a table scan?
Michael Kennedy: There's all these things, right?
Michael Kennedy: And that has to be determined for a query.
Michael Kennedy: So it could be kept around and reused better, potentially.
Michael Kennedy: And maximize the connection throughput.
Michael Kennedy: So there's a bunch of stuff in here and some examples and so on.
Michael Kennedy: Again, similar programming model with connection with async width,
Michael Kennedy: but you get a connection from the pool.
Michael Kennedy: Somewhere down here, though, there are some stats, I do believe.
Michael Kennedy: Yes, the very, very bottom.
Michael Kennedy: Let's see.
Michael Kennedy: It says just doing 100,000 complex read operations across 20 workers with a reasonable-ish database setup, 5 million comments, 10 million likes, 100,000 posts.
Michael Kennedy: And so like real data, not just like there's three items, query them, which one is, you know, which one's bigger than one.
Michael Kennedy: Anyway, with all that, it says what's your throughput without the pool?
Michael Kennedy: You get 3,000 operations a second with it.
Michael Kennedy: You get 6,000.
Michael Kennedy: basically for all the metrics you care about it's like a 2x improvement almost not quite but almost
Michael Kennedy: so like throughput's almost double the latency's almost half more than half um better than that um
Michael Kennedy: so on right so instead of 60 milliseconds it's 20 milliseconds response time that kind of thing so
Brian Okken: why not you know if this is easy to use so you're gonna like maybe i'm dense but the i can use this
Brian Okken: and I can have multiple async
Brian Okken: or multiple parts of my process
Brian Okken: accessing the same file at the same time?
Michael Kennedy: Yeah.
Brian Okken: Okay.
Michael Kennedy: Yeah, SQLite supports concurrent access.
Michael Kennedy: And especially if you're reading,
Michael Kennedy: there's no problem reading the file in parallel.
Brian Okken: Yeah.
Michael Kennedy: Right?
Michael Kennedy: So, yeah.
Michael Kennedy: Anyway, if you're doing SQLite stuff
Michael Kennedy: and you're doing async stuff,
Michael Kennedy: check this out.
Michael Kennedy: There may also be a SQLite pool that is not async.
Michael Kennedy: I have no idea.
Michael Kennedy: I haven't looked at that.
Michael Kennedy: But once you get to the point where you're like,
Michael Kennedy: I'm worried about concurrent speed access to my database,
Michael Kennedy: you know what, you're probably already in async land anyway.
Michael Kennedy: So here you are.
Michael Kennedy: Yeah.
Brian Okken: So the answer is, yes, you're dense.
Brian Okken: And I'm going to answer you anyway.
Brian Okken: But no, thanks.
Michael Kennedy: Yeah, yeah.
Brian Okken: All right, over to you.
Brian Okken: OK.
Brian Okken: I am going to--
Brian Okken: I'd like to talk about dependencies a little bit.
Brian Okken: Last week-- I think it was last week--
Brian Okken: We talked about pipdeptree and uv pip tree.
Brian Okken: And those are great things.
Brian Okken: This sounds similar, but it's not.
Brian Okken: I'm going to talk about DEPTRY, D-E-P-T-R-Y.
Brian Okken: And I'm pretty sure this was recommended by somebody,
Brian Okken: but I couldn't find the reference.
Brian Okken: So I'm sorry for losing your name,
Brian Okken: but thanks to everybody for suggesting topics.
Brian Okken: So Deptree is D-E-P-T-R-Y.
Brian Okken: And what it does is it's a command line tool to check for issues with dependencies in a Python project,
Brian Okken: such as unused or missing dependencies.
Brian Okken: So the idea is like, so I appreciate the unused part.
Brian Okken: The missing dependencies I'm probably going to catch and test, but hopefully,
Brian Okken: but maybe you don't have thorough tests.
Brian Okken: So if you're importing something and it doesn't show up in your requirements file or your
Brian Okken: Python project.toml, it'll flag that.
Brian Okken: And the reverse is true too.
Brian Okken: So if you have a dependency listed, but maybe you refactored your code and you're not using
Brian Okken: that dependency anymore, it'd be nice to find out that you don't need it.
Brian Okken: So that's pretty much what it does.
Brian Okken: But I really wanted one.
Brian Okken: And it's pretty easy.
Brian Okken: You install it in your project and then you run it.
Brian Okken: and it scans everything and lets you know if,
Brian Okken: hey, you've got, for instance, NumPy is imported,
Brian Okken: but you didn't declare it as a dependency.
Brian Okken: And it does have this idea of development in dependencies
Brian Okken: versus project dependencies,
Brian Okken: and that's the part that tripped me up a little bit.
Brian Okken: That's the switch.
Brian Okken: It's either development dependency or a project dependency.
Brian Okken: And it's unfortunately super easy to get started and really easy to get tripped up by it.
Brian Okken: And I got tripped up because I use optional dependencies for tests often.
Brian Okken: So I'll do something like list test.
Brian Okken: In my project, I'll say project optional dependency.
Brian Okken: For test, I've got pytest and all my pytest plugins.
Brian Okken: And then maybe doc for docs for all of my make docs or something to build the documentation.
Brian Okken: Pretty standard.
Brian Okken: But what Deptree does is it finds these optional dependencies and just includes them in your normal dependencies because it might be your CLI or your GUI, which is interesting.
Brian Okken: I guess I don't get why your GUI or your CLI would be optional, but maybe two choices.
Michael Kennedy: I don't like it either, but I think I've seen it like I want to install this and only have the CLI or I want to install this.
Michael Kennedy: And I do also want to have the GUI and the GUI install might be super heavyweight.
Michael Kennedy: You know what I mean?
Michael Kennedy: It's just a way to say I want less instead of like the union of all possible use cases.
Brian Okken: Actually, I.
Brian Okken: Oh, cool.
Brian Okken: I've got a.
Brian Okken: I wonder if I can work this as a test in test suites because there's times where I want some.
Brian Okken: Anyway, I'm getting off on a tangent, but I think this would be fun to play with with test suites.
Brian Okken: Why I'm going down this rabbit hole is because the most common thing in the usage and configuration,
Brian Okken: it's like buried in here.
Brian Okken: But if I look for a pytest, I'm going to have to look for it a couple of times, I guess.
Brian Okken: Here we go.
Brian Okken: So optional dependencies test of pytest, you have to list it out as you have to add this
Brian Okken: big pip dep tree or tool dot dep tree and then pep621 dev dependency groups.
Brian Okken: this is kind of verbose guys, but that's what you got to do.
Brian Okken: And if you do that, it all works fine because I just like tried this out on a
Brian Okken: simple project and it said, you're in, you've included pytest,
Brian Okken: but you don't import it anywhere. No, I don't import it anywhere.
Brian Okken: I'm using it for my test.
Michael Kennedy: Do you understand what this is for?
Brian Okken: So I'm a little thrown that I think,
Brian Okken: I think maybe I'll suggest that this, that the,
Brian Okken: their example of using your depend that the dev dependency groups are at the
Brian Okken: very least test and docs.
Brian Okken: And I think that that should be the default.
Brian Okken: I don't think you should have to declare that.
Brian Okken: You know,
Brian Okken: if,
Brian Okken: if you've got a tests or docs,
Brian Okken: it's,
Brian Okken: it's probably a development dependency,
Brian Okken: not.
Brian Okken: But anyway,
Brian Okken: I had fun with it.
Brian Okken: I tried it out.
Brian Okken: I do like the,
Brian Okken: it's not a whole bunch of rules.
Brian Okken: The rules are like projects should not contain missing dependencies,
Brian Okken: should not contain unused dependencies,
Brian Okken: should not use transitive dependencies.
Brian Okken: That's interesting.
Brian Okken: Yeah, I kind of agree.
Brian Okken: You don't depend on-- if something's
Brian Okken: depend getting imported or installed because you
Brian Okken: installed something else, that third party package
Brian Okken: might refactor and not include that.
Brian Okken: So yeah, you should--
Brian Okken: Yeah.
Brian Okken: --transitive.
Brian Okken: Anyway, I think a fun project.
Michael Kennedy: And yeah, I'm going to check it out a little bit more.
Michael Kennedy: Very cool.
Michael Kennedy: Henry out there says those tests and doc dependencies should be dependency groups nowadays.
Brian Okken: Okay.
Michael Kennedy: I appreciate that.
Michael Kennedy: I don't do nuanced stuff enough to know.
Michael Kennedy: So yes, thanks, Henry.
Michael Kennedy: Thanks for that homework, Henry.
Michael Kennedy: Yes, exactly.
Michael Kennedy: Thanks for the homework, man.
Michael Kennedy: So you know what?
Michael Kennedy: I could find myself on a server or just the terminal, and I'm trying to figure out why are some of my dependencies missing?
Michael Kennedy: Where are my files even?
Michael Kennedy: What's going on, Brian?
Michael Kennedy: And I came across this thing called Juftin Browser.
Michael Kennedy: Drop the E.
Michael Kennedy: So it's a little bit too Web 2.0y, but it still has the O,
Michael Kennedy: so I don't really know what that means.
Michael Kennedy: Anyway, what it is, is this is a really neat tool
Michael Kennedy: that is basically an interactive keyboard-driven
Michael Kennedy: and mouse-driven experience, like a Finder or Windows Explorer,
Michael Kennedy: but for your terminal and works over SSH.
Michael Kennedy: So if I SSH into a server, I can say Browser
Michael Kennedy: in a folder and it gives me a tree of all the folders i can arrow through them i can click
Michael Kennedy: through them and then expand and when you click on them it will show on the right the file and on the
Brian Okken: left the tree of the area starting from where you ran it and down isn't that cool that is pretty cool
Michael Kennedy: yeah and it has yeah it has um basically the viewing for the files it has context highlighting
Michael Kennedy: you can even show images and a couple other things like that so really neat and i think if you're
Michael Kennedy: doing anything super terminal based i know you can run on your local machine but i don't know here's
Michael Kennedy: a little tip for people who don't know if you're in a folder on mac os you can type open space dot
Michael Kennedy: and that will just bring a binder there in windows you can say start space dot and it will open up
Michael Kennedy: windows explorer focused in that folder so if you're in the terminal you want like a brow like a
Michael Kennedy: gooey like thing you're pretty close you're pretty close to having it you got to type browser anyway
Michael Kennedy: if you want to get this thing to start.
Michael Kennedy: But if you're on an SSH connection to a server,
Michael Kennedy: well, there is no alternative but to just LS your way through.
Michael Kennedy: And this is a really nice way to just kind of flip through
Michael Kennedy: and exploit what is in here.
Michael Kennedy: And as you move through the files,
Michael Kennedy: it displays them with syntax highlighting.
Michael Kennedy: I like it.
Michael Kennedy: I think it's super, super useful.
Michael Kennedy: It's going to be part of my server maintenance toolkit,
Michael Kennedy: I think is what I'll say.
Brian Okken: Yeah, it's fun.
Brian Okken: I, you know, I'm also one to possibly just use open.
Brian Okken: for that, but also
Brian Okken: or just cheat and
Brian Okken: just say code space dot and
Brian Okken: open
Brian Okken: and have the tree directory.
Brian Okken: I think the O is necessary
Brian Okken: in the name so that it's
Brian Okken: bro. So bros or
Brian Okken: maybe. Bro.
Michael Kennedy: Yeah.
Michael Kennedy: If you don't, it's not on the
Michael Kennedy: GitHub, I don't think, but if you click their
Michael Kennedy: domain, which is
Michael Kennedy: effectively like a read the docs type of thing,
Michael Kennedy: you can actually see it in action.
Michael Kennedy: with a little animated screen recording.
Michael Kennedy: We love animated screen recordings.
Michael Kennedy: Yes.
Michael Kennedy: So, so nice.
Michael Kennedy: So.
Michael Kennedy: Cool.
Michael Kennedy: All right.
Michael Kennedy: What you got extras?
Brian Okken: I just have a show and tell extra
Brian Okken: because I went to an estate sale a couple weeks ago
Brian Okken: and I got a fun gift that,
Brian Okken: or a fun little thing that I just picked up.
Brian Okken: And so I was going to show it off, show and tell.
Brian Okken: I got this book called Micro,
Brian Okken: Understanding the Micro.
Brian Okken: And it's microcomputers, how they work and what they can do.
Brian Okken: And I flipped.
Brian Okken: It's sort of fun.
Brian Okken: It's got like, you know, it's for kids and stuff.
Brian Okken: But in the back, there's a buyer's guide.
Brian Okken: And I flipped back.
Brian Okken: I'm like, well, does it have mine?
Brian Okken: And yeah, sure enough, the TRS-80 color computer.
Brian Okken: That was when I started.
Michael Kennedy: Okay.
Brian Okken: Fun little book.
Brian Okken: And I haven't read much of it yet, though.
Brian Okken: but it should be fun.
Brian Okken: It even talks about basic programming
Brian Okken: and stuff like that.
Brian Okken: It's fun.
Michael Kennedy: Nice.
Michael Kennedy: You see, Brian,
Michael Kennedy: I was definitely later
Michael Kennedy: in the computer hardware game.
Michael Kennedy: My brother had a Commodore 64,
Michael Kennedy: but I saved up when I was in high school
Michael Kennedy: and I got myself a 486 DX,
Michael Kennedy: not the SX,
Michael Kennedy: but the one with the floating point processor
Michael Kennedy: and 33 megahertz.
Michael Kennedy: That's where I started off.
Brian Okken: I think that's close to what I had.
Brian Okken: I think I must've been ahead of you a little bit.
Brian Okken: I bought a 486 IBM 46 when I was in college so that I could do homework on it.
Brian Okken: And I think the first thing I bought was Turbo Pascal for it.
Brian Okken: Nice.
Michael Kennedy: I think the first thing I got was MechWarriors.
Michael Kennedy: Yeah.
Michael Kennedy: All right.
Michael Kennedy: Awesome.
Michael Kennedy: Well, there's a whole bunch of stories from that era, but let's go back to this era.
Michael Kennedy: And I just want to say, since you gave the recommendation of John Papa's Peacock, I've
Michael Kennedy: been playing with it.
Michael Kennedy: It is so good.
Michael Kennedy: that's fun right it is really really useful and what i didn't realize the way it works is if you
Michael Kennedy: are in something like cursor or vs code or whatever and it has you have to create a workspace not just
Michael Kennedy: open a directory but once you create the workspace it embeds your like styling for that project into
Michael Kennedy: the workspace file so it syncs across machines naturally by just doing get push get pull oh and
Michael Kennedy: So yeah, it's a little bit extra like that.
Michael Kennedy: So that's pretty cool.
Michael Kennedy: Anyway, I just want to give a shout out
Michael Kennedy: to a follow up to that, I suppose.
Michael Kennedy: Like, yeah, that was awesome.
Michael Kennedy: Still is.
Michael Kennedy: Cool.
Michael Kennedy: I guess I have, do you have more extras?
Michael Kennedy: No, without further extras.
Brian Okken: I had one that I kind of forgot to say.
Brian Okken: I am still working on the Lean TDD book
Brian Okken: and I'm almost done with the building
Brian Okken: on test-driven development chapter.
Brian Okken: So finally, with a book like TDD in the name,
Brian Okken: I finally talk about TDD in it.
Brian Okken: I haven't released that yet,
Brian Okken: but I'm hoping to release that later today
Brian Okken: or maybe tomorrow.
Michael Kennedy: Oh, very cool.
Michael Kennedy: Awesome.
Michael Kennedy: I love it.
Michael Kennedy: Anyway.
Michael Kennedy: That's great.
Michael Kennedy: I love the idea.
Michael Kennedy: And Brutus out there says,
Michael Kennedy: Peacock is awesome.
Michael Kennedy: I used it since last week
Michael Kennedy: when you talked about it, Brian.
Michael Kennedy: Thanks.
Michael Kennedy: Cool.
Michael Kennedy: Yeah, I love it.
Michael Kennedy: Yeah, I do too.
Michael Kennedy: All right.
Michael Kennedy: Let's do our joke.
Michael Kennedy: So, you know, people have threats.
Michael Kennedy: They can be empty threats
Michael Kennedy: or scary threats.
Michael Kennedy: You know, like,
Michael Kennedy: I'm going to tell the world about this thing that you did weird.
Michael Kennedy: Or I'm going to find you.
Michael Kennedy: I'm going to punch you in the gut or whatever.
Michael Kennedy: But that's not a very common thing that programmers do.
Michael Kennedy: Now, programmers have a different version.
Michael Kennedy: I will find you and I will install Linux on your computer.
Brian Okken: Yeah, that's extreme.
Michael Kennedy: Yeah, you know you've messed up when someone gets over and you're like,
Michael Kennedy: Aurora? All right. Who did this? What is this? Reminds me of the, I'm having the bios flavor
Brian Okken: of the slushies or the frozen yogurt or whatever. Yeah. I will downvote your Hacker News article.
Michael Kennedy: No. Oh yeah, exactly. I will definitely downvote your Hacker News article.
Michael Kennedy: Or, you know, this also reminds me of like some of the jokes people used to play. Oh my goodness.
Michael Kennedy: especially with Windows, if you could change the background image.
Brian Okken: Oh, yeah. To the blue screen of death.
Michael Kennedy: Change the background image to the blue screen of death.
Michael Kennedy: Or I know when Vista came out, people were super like,
Michael Kennedy: do not put this on my computer.
Michael Kennedy: And the IT people were installing it.
Michael Kennedy: I know someone who took a screenshot of Vista,
Michael Kennedy: put it onto someone else's computer,
Michael Kennedy: and then tasked their Explorer or something like that.
Michael Kennedy: And so they didn't have any.
Michael Kennedy: Oh, that's funny.
Michael Kennedy: They had no thing overlaying it, so it just, like, no, they didn't.
Michael Kennedy: And they, like, click around.
Michael Kennedy: Like, I told you it wouldn't work.
Michael Kennedy: Nothing even clicks here.
Michael Kennedy: Yeah.
Michael Kennedy: I will find you and do stuff your computer is pretty fun.
Michael Kennedy: But this one is I will find you and install Linux in your computer.
Brian Okken: That's funny.
Brian Okken: Yeah.
Brian Okken: Be careful whose child you had booked.
Michael Kennedy: Exactly.
Michael Kennedy: Well, I'll tell you what.
Michael Kennedy: I'm not actually going to go install Linux on anyone's computers,
Michael Kennedy: other than particularly mine.
Michael Kennedy: So no threats here.
Brian Okken: Yeah.
Michael Kennedy: Although, Henry does point out that these days, maybe the opposite is more threatening.
Michael Kennedy: I'll find you and I'll steal Windows 11 on your computer.
Michael Kennedy: Yeah.
Michael Kennedy: Oh, there's a lot of bad ideas shown in the chat.
Michael Kennedy: We're not going to share.
Michael Kennedy: They're great, though.
Michael Kennedy: Made me laugh.
Michael Kennedy: No, they're good.
Michael Kennedy: Thank you, everyone.
Michael Kennedy: See you all later.
Michael Kennedy: Bye.