Hello and welcome to Python Bytes, where we deliver Python news and headlines directly to your earbuds.
This is episode 478.
I am Michael Kennedy.
And I'm Brian Okken.
This episode is recorded on May 4th, 2026, brought to you by us and all the things we're doing.
I'm sure we'll mention something during the show somehow.
I've got a few cool updates to discuss.
If you want to connect with us on social media, maybe submit a topic that you think we should pay attention to.
Check us out on all the social medias.
You can find us on the show page, episode page.
Pretty much everyone has a link to all the things there.
Sign up for the newsletter.
It adds way more than just show notes or, hey, we published an episode.
It's got a bunch of cool extra information that we put in there.
So check that out.
And with that, Brian, I think we should get started.
What's your first topic?
I'm going to talk about profiling explorer.
So this is a profiling explorer is a tool from Adam Johnson of lots of things Django and Git related fame.
So Adam, so how did I see this?
I don't know.
Oh, yeah.
He had a blog article that he released last month that somehow I just found out.
I read today.
Introducing profiling explorer.
Actually, I picked it up yesterday.
But anyway, so this is kind of fun.
This is a says I've made it another package.
Wait.
Anyway.
So what do we have here?
We have a way to profile.
We have lots of ways to profile Python code.
But this takes the output of the profiler, the C profiler, and pops it into a table that you can interact with.
So this lovely table that also has dark mode.
He shows it in light mode, but it also has dark mode.
And it's got all the normal stuff you'd think of for profiling.
You've got the cumulative time, the percentage of your time in a certain place, and the number of calls that go to this place or this thing.
So but you can filter on the filters kind of cool.
So you can click on the calls or the internal time or cumulative time column headers to sort by that, which that's where I usually start is certain by the percentage of the time spent somewhere.
Anyway, then you can also do there's a search box.
So you can filter on like if you like even if you grab all of the time, but you're really looking at a subcomponent that you're working on, you can just look at that and see where it's small.
So like that's often the time where I'm often grabbing, looking at the profiling documentation is how do I filter down to just the thing I want to care about?
And sometimes it's easier just to grab it all.
And then and then just using this, you could filter in exactly what you want.
So yeah.
And there's a hover features and caller and colleagues.
And I guess look through the article to figure out what what this is all about.
But it looks really slick.
I haven't tried it yet, but I'm going to probably this week.
So it looks fun.
And profiling is certainly finding a needle in a haystack.
So all the UI, all the search you can get is very good.
Yeah.
And there's like profiling often has like there's some people that like the flame graphs.
I've never gotten the flame graphs to work in my brain.
I just don't get them.
So so something like a table works for me.
I like this.
Yeah.
I really like the call call hierarchy type of thing.
It's almost the call call stack, but it's split if it takes different branches that you see in like PyCharm and stuff.
Yeah.
That works for me.
But still, those things can be too noisy.
So very cool.
Yeah.
Nice.
Now let's bump over and talk about reverting the incremental GC in Python.
Like what?
So this is a, I don't know who just, I think just the core developers and steering council as a group decided on this.
But the post is by Hugo Van Commande.
And it's just entitled reverting the incremental GC in Python 3.14 and 3.15, which is pretty wild.
And there's, this is on discuss.python.org.
And so there's a bunch of back and forth here.
So let me give you some of the highlights.
Okay.
So Python 3.14 shipped with a new incremental garbage collector.
So I believe the way it worked previously is when a garbage collection happened.
And maybe I should point out why garbage collections happen.
So Python is a little weird in that it has two types of memory management.
Both of them automatic.
You don't worry about them.
But they're two ways of managing memory.
And they happen in different scenarios.
Okay.
So the primary, by far, way that memory management happens is by reference counting.
You get a variable.
It has one reference.
You pass it to a function.
Now it has two references.
That function puts it into a list, but then returns.
It goes up to three and then back to two.
You throw away the list.
And then the variable goes away.
Okay.
Reference count hits zero.
Delete.
Right?
Reference counting works great.
It's super fast.
It's immediate.
Except it does not work great when you have a cycle.
Right?
I've got something, two objects that point to each other for some reason.
All of a sudden, their reference counts never hit zero.
Memory goes through the roof.
You're toast.
So what we're talking about is the thing, the garbage collector that doesn't use reference counting, but actually traverses all of the references and then looks for those cycles that are abandoned, but themselves never went to zero and collects it.
Okay.
So there was a new incremental garbage collector added that the way it worked now is you would have different generations.
Those generations would run.
When it was time for a collection, the entire app stopped.
Garbage collection was checked.
These cycles were checked.
And then the app carried on.
So the incremental one tries to improve latency.
Say like, look, we don't have to stop the program entirely.
We're going to do a little bit of garbage collection, a little bit more running, a little bit more garbage collection and so on.
Of course, the picture of garbage could change over that period.
Right?
Anyway, that was added.
But it turns out production reports started to come in for severe memory pressure.
Neil measured up to five times peak memory on pathological cyclic workloads.
And cyclic is the important part because that's actually where GC actually does anything.
It actually makes, you know, actually does the cleanup.
And that pushed the core team and steering council to revert it.
It's in 314, but it's going to be taken out of 314.
And it's going to not actually make it to 350, which is pretty extreme, I think.
Right?
It takes a lot to get something into Python, but once it's in, it's rarely taken out.
All right.
So this is actually the second time the incremental GC has been pulled back.
It was reverted right before 313 first came out.
As they were like, oh, is that quite ready?
And then it got into 314 without going through the PEP process.
So this is a bit of the tricky stuff.
However, the benefit was real.
So like they were trying to reduce latency.
So with the incremental one, the max GC pause times for one example was one millisecond versus 26 milliseconds with the old one.
So that's great.
Except for it was just blowing up the memory usage of things that cared more about memory and less about latency.
And a lot of places we run Python care more about memory than they care about very, very small pauses.
You know, think like APIs and web apps and anything that runs on a server or in the cloud.
Memory is probably the most expensive resource.
Right?
So that's not great.
So Hugo decided we're going to ship 314.5 early with the revert.
And Gregory Smith floated the idea of a 314.5 RC1, a release candidate for a shipping version of Python, which would be interesting.
Okay.
And then Tim Peters jumped into thread, doing a bunch of live forensics on Windows, running a toy DQ program that should cap at one gigabyte.
And it used up to 15.6 gigs on a 16 gig machine.
So that's not great.
And this is really bad.
He discovered that Gen Zero collections effectively never fired under this new collector.
That's the one that gets most of them and it's the cheapest to run.
So that's a big problem.
Anyway, this might sound bad, but Tim points out that CPython has had a chronic shortage of real world GC benchmarks.
High performance, the test suite that they run Python on for performance considerations, says it has basically no interesting cyclic workloads and users almost never share real data.
So core devs keep flying blind.
And circling back to your previous topic, right?
Is Adam Johnson published a blog post along the thread of a real memory leak in Django migration systems caused by the incremental GC with where you have to call GC collect manually to fix it.
All right.
So it may or may not come back for 3.16.
If it does, it was going to be restarted through the PEP process.
So a lot going on here.
That's crazy, right?
Well, yeah.
But I also hope that, I mean, Tim's comment is like, we kind of flew past it, but it's really, it's really important that the cyclic workload, having some of those in a benchmark is important.
But if you can come up with a pathological way where it doesn't work as well, it shouldn't crash.
It shouldn't be like, even an incremental should eventually go, you know what, we need to shut down and clean things up if necessary, I think.
but, but we also need to have a benchmark that's more realistic and it's hard to tell what realistic is because we're doing, Python's being used for everything from, you know, from, from particle physics to web pages.
so who knows?
I have a suggestion for them.
I agree with you.
I have a suggestion.
One of the areas this shows up very often is in ORMs.
Oh yeah.
Right.
So imagine I've got a user and, maybe a course and then a user activity, right?
So if I go run a query, you can send a database for all those things that are in, maybe the user activity has a user ID, but it also has a like reverse lazy loaded back to the user itself and back to the course itself.
But the user's holding onto their activity.
Cause they've got like a list of activities, which was also a lazy loaded and you like tell SQLAlchemy or something like we're going to do eager loading and all these things does creates tons of cycles just by doing database queries.
Like I've seen that kind of stuff where the GC makes a difference on my web apps that actually do a lot of database things.
So maybe they could come up with like a real interesting web app database query sort of example, and just use put SQL, a static SQLite database that's in there and integrate that.
I mean, I'm sure there's a hesitancy to say, well, the way you run PI performance is you're going to fire up this database and this Redis queue.
And then you're going to like, you know, like the infrastructure doesn't make any sense, but you could do it with SQLite.
And I think you could, you could come up with some interesting, useful examples that have tons of data.
Cause just fill the database, you know?
Yeah.
Anyway.
Interesting.
I think it's worth considering.
It is worth considering.
Oh, I got to hop over to my next topic.
Nick's this, speaking of discussion.
So this is just, I guess, I guess I'm just like passing along a discussion.
I was amused to, to read about.
so this is, few, I, it changed today, yesterday that the topic changed.
So I was surprised to find out that Microsoft, and VS Code enabled AI coauthor by default.
So, and I'm, I'm like, what really?
So I read a little bit more about this and really it's, so you can, you can do get commits and stuff to that have, whether or not you've, you know, whether or not AI contributed to the code.
And instead you used to be able to just like say, it used to be only of like get or your AI is actually committing.
but, but, you know, copilot wants to get credit if they're doing a lot of work, I guess.
I don't know.
But, so, there's a flag that you can set.
That's the get dot add, add AI coauthor configuration.
And there, it was started with off and they defaulted.
They won't change it to default of all.
and, it isn't all the time, but if there's something in here that tries to detect whether or not you used any, any of the code was, contributed by an AI workflow or anything.
And I'm not sure about all the details, but people freaked out basically because like, I was like, even if I, even if I run a, like a copilot to try to figure out something, I may
have rejected everything or, or something and, and, or maybe my code looks like something that the, I don't know, how does it detect it?
I'm not sure.
and, and I don't think that's right.
And basically I just don't think it's right.
Well, I was about to talk about that.
And then I noticed that I was reading the comments this morning and found out that there was a follow-up and the follow-up was just yesterday, changed the default back to off.
so, and then, and then it devolved.
They closed the comments, even in one day, they closed the comments because basically the comments turned into, why are you even using VS Code?
You should use VI or, you know, Emacs or, or what are the other, some of the others and stuff.
So anyway, I use, I use, I use a lot of editors, not a lot, a couple, but VS Code is one of them.
and I was the, I think the main takeaway from this is I don't trust them.
I'm going to go in my settings and, go ahead and whatever this, no, I can't find it.
The setting was, was like, whatever.
Oh, here it is.
The, the ad AI coauthor.
I'm going to just go ahead and set that to off in, in my, in my settings file, because I don't trust them to turn it back on later.
anyway, I think this is crazy.
First of all, let me defend the people who say VS Code.
Where, where folks are saying you should use them or Emacs.
I'm not, I feel like a lot of those editors encourage bad, bad design practices, right?
Whereas proper IDE like things are a little bit better.
So I think that that's fair.
I don't think they should take that personally, but this AI coauthor stuff is just a, so that was kind of put the defense up before we started hacking on them.
So I think I, this is the first time hearing this, Brian, this is, this is garbage.
Now I haven't noticed this because I don't use copilot.
Cause I have more respect for my work time and just use cloud code, in some kind of VS environment with the extension to be clear.
And I also hate it if cloud does it, but every now and then cloud does it.
And it drives me crazy.
If I ask it for a commit message, it'll sometimes give me a bunch of stuff and then coauthored by cloud code.
And it'll like at mention their GitHub username or whatever.
And like delete, delete, delete, delete, delete.
So I've never seen this.
So where does it show up?
Does it, is it like behind the scenes or does it show up?
The most common place I've seen it is in pull requests, but I've also seen it in commit messages.
So let's just say it's a pull request.
Okay.
So you might go, I've not, is it in the message though?
Yes.
So I've, I've not used it coauthor, like I copilot, like I just said, but I've gone to cloud and I've said, Hey, you know, there's a bunch of stuff going on here.
And I kind of forgot all the details that changed.
Like, wouldn't it be a little more thorough if I said, Hey, Claude, look at all the pending changes on this branch since I've branched it and give me a nice summary and overview of actually what's changed instead of the stuff that I just intended to change.
Maybe something else, you know, like maybe I ran the linter and it changed a bunch of stuff, but when I really only changed one line, but I would like to talk about, you know, whatever, something like that.
It will say, here's the title, here's the description that you put, and it'll say all of it's describing and the bottom, it'll have a last single sentence paragraph that says coauthored by Claude code at anthropic or at Claude or something like that.
That's lame.
I'm like, screw this.
So then I'll delete that, which is fine.
But you can also just say, Claude, create a pull request on GitHub for me.
And it'll do that beautifully.
But you know what shows up at the bottom of that pull request description?
Coauthored by Claude.
So Claude doesn't do as often, but it sounds like, you know, Microsoft has gone absolutely bonkers over AI-ing everything.
And I think that is a huge mistake.
I think they have 40 different products named CoPilot that are actually different things like in Office 365 CoPilot, Windows CoPilot, CoPilot on GitHub, CoPilot and VS Code.
You know what I mean?
There's just like, there was a mandate that everybody, you know, a few years ago, 2023 or something like that, like every team that builds something at Microsoft needs to have some form of AI in it.
And those were all independent projects and initiatives.
And the adoption isn't that great.
So this to me feels like a poor attempt, a bad attempt at kind of trying to growth hacking CoPilot back into the conversation, right?
Yeah, maybe.
Yeah.
Think of like early days of Hotmail, which is completely forgotten.
But one of it's really the things that was kind of a secret to a success, this is common now, but it wasn't then, is every email you sent was sent by Hotmail.
Get your own one gigabyte free web email.
And every single email had a link back to it.
And people go, oh, you can have web email.
That's cool.
And like, like that was, and I feel like it's that.
Social media stuff too.
People would be like, you know, this post written on Mona on iPhone or something like that.
Yes, yes, exactly.
Yeah.
There's a lot of that.
So I think it's, it's got a strong ick factor.
I just checked my default VS Code, which I don't know whatever it was, but it had this on.
And so I just turned it off and I'm going to go do a thorough cleansing.
But I think it's a tree falls in the forest, but no one, there's a here sort of example for me.
Cause like, I don't use CoPilot.
So if I did, it would put the marking on the co, the co, attribution on it, but I'm not going to use it.
So it's not a problem.
I actually don't get the CoPilot hate because I I'm using it, but I've been using it
from the start and it's just like mostly code completion and, and a, you can open a window to, to open AI chat if you want.
But, the, the, whatever settings I have are not intrusive.
They were, they were intrusive for a while and I did something and they're not that bad anymore.
And the comments, the suggested comments don't get in the way.
And, and I'm, I'm, I appreciate it.
And the, and I do use VS Code, but I also use Vim mode.
so I, it's basically a, a big wrapper around Vim as far as like I'm using it.
I do like the other thing I really like about it is, the integration with get so that I can, I can find out all the stuff I've changed and use do diffs easy and stuff.
So I do like it.
And also there's a lot of people using cursor and you can't hate on VS Code and like cursor because they're the same thing.
so they're not exactly the same thing, but it's a fork.
So anyway, a hundred percent, I turn off the autocomplete for all those tools.
I don't like them, but so my, my view into this world is just the agents, you know, it's been, let's, let's move on to the next topic, Brian.
It's been, Ooh, you wouldn't know it.
We had literally a heat advisory.
It was almost 90 degrees yesterday.
It was terrible.
Boy, was it freezing in Django land.
Let me tell you.
So I want to talk about something called Django freeze.
And I think this is a super cool project.
It doesn't have very much attention.
It's only got 117 stars and 16 forks.
It's the kind of project that's really low risk, like really low risk, but has a ton of benefits.
So the idea with Django freeze is I've written a Django app and I'm thinking about how do I deploy it?
Maybe it's driving its content from the database.
Like it's got a, it's like an e-commerce store and it's got, here's all your categories and here's the products you're selling and so on.
Those come out of the database, but maybe they change infrequently or whatever.
So you could use Django freeze to just convert a static HTML version of your site and deploy that somewhere.
Have all the categories, have all the products, have all the little backlinks and all that kind of things that you might have, whatever your app does.
But the deployment and operation, the DevOps side is static files, which is incredible.
Oh, cool.
It's good for operational.
Like your static files can't go down unless just your server doesn't work anymore.
You know, like there's very few things that can go wrong.
You know, it's not like you're going to, well, I ran out of memory or there is, I don't know, like some kind of issue between the caching and like just all the issues you have running real websites.
Like with static sites are so delightful.
Put them up, log as the server's online, things are good, you know, and you can host them for free in many places.
So if you've got a Django site and you think really it kind of could be static site, but I like to work in Django.
I don't want to work in Hugo or something like that where it's foreign or weird.
Hugo is a really weird, even though it is good.
You could just write in one, write in Python, write in your favorite web framework, but then turn it into a static site.
And I really think this is a cool idea.
It's, you know, sort of a peer of Flask Freeze, I think is the name.
Yeah, I think it's Flask Freeze.
What do you think?
Cool, right?
Yeah.
And one of the things I think one of the places where I'd probably, that I'm actually thinking of using this, I'll try it out, is like a SAS, for instance.
You've got the actual application that needs to be Django or whatever, you know, let's say you've written it in Django and you want your sales site, you know, you've got two
sites, you've got the actual application and then you have your like sales site.
If they look really close, then there's no, the transition's really easy.
So you could have a lot of your blog content or whatever on the static side.
You're trying to hit lots of random traffic and then, and then flip over to your application and, and the user won't notice that much of a difference because the, it's the same look and stuff.
So that's, yeah, that's a perfect use case or like the docs for your SAS, you know, like user manual, all that stuff could just all be static, static, static.
Yeah.
That's pretty cool.
I'll give you one more example.
I talked to, to David Flood from the Harvard sort of humanities enablement team, I guess is a simple way to put it.
And he and his team go around sort of like on internal consultants or whatever for different researchers who are not really programmers or web people and help them set up websites,
portals, data management, data exploration, et cetera.
And one of the areas that he talked to a lot about is like, what happens if you create something like a Django site or anything else as part of a grant, a three-year research project, but then the grant is over.
You're paying a hundred dollars a month to host the Django site, but now who's going to pay for that, right?
You're, you don't want to pay for it because you don't have any grant money left, but if you don't, it's going to go away, which is a big hassle.
Yeah.
That'd be cool to just be able to convert it to a static.
It's not going to update anymore and it can be something you can reference and stuff.
So.
Yeah, exactly.
So you've got this project that needed a dynamic site for a long time, but then all of a sudden it no longer is supported or whatever, but you don't want it to vanish from the internet.
So hit it with one of these, you know, convert to static sites.
I think it's a really cool idea.
Yeah.
It is cool.
Yeah.
Indeed.
You know what else is cool?
Extras are cool.
Yeah.
I'll let you go, go next on the extras.
Okay.
I need, I like accidentally unshared.
So I'll, I'll share it just in, I'll be just a second and here we go.
All right.
So this is, is we were talking about, thinking about AI a lot.
I know a lot of you have kids out there, or maybe you are, going to college or high school or something like that.
and if you are, thanks for listening.
That's awesome.
Anyway, I ran across this article this morning.
It's called thinking less, trusting more gen AI's impact on students, cognitive habits.
And actually this isn't an article.
This is a, an abstract from a study from Oregon state university.
and like actually the top, there's like a objective and a method and result at the top, but it's rather, it's rather it's, it's not too hard to decipher the results
looking at this, but it's still in like, you know, it's, it's a, scientific paper speak.
So, if you pardon the flyby, the best way to read this is to go all the way down to the bottom.
Oh, not all the way to the, to the references, but there's a conclusion.
And this is, this is actually interesting.
I think it's really interesting about students using AI and stuff.
So I'll just read out the little bit here.
If routine reliance on gen AI during formative years, and I don't remember what formative years are, but whatever, changes students' willingness to engage in effortful thinking.
Many may enter professional life without having developed the intellectual habits that earlier generations developed through practice that yet this, this need, this need not be inevitable.
cognitive, the cognitive debts.
Anyway, basically, the use of AI and the way AI is designed, like things like chat, GPT and stuff need to be modified so that, learn both learning environments and gen
AI systems are modified to preserve human agency and support genuine complimentary, complimentarity.
I didn't know that was a word.
generally division of cognitive labor between both human and AI contributions should be meaningful, meaningful setup.
And so that neither is displaced.
Basically you need to, and I kind of agree.
I think even when using, like Claude and stuff like that, I think that you can get them to ask you, you can say, Hey, do this task.
And if you run into issues, ask me about it.
I think that should be the default.
I think it should, it should default to, even if, even if you don't want to get interrupted, just like, you know, you want it to have like flow mode and just like get stuff done.
It should pull out points and say, Hey, these are some of the decisions I made.
could you review this spot, this pot, this spot?
and what do you think of that?
And we could change it, change it if necessary.
And I think there's minor tweaks that could be done with a lot of these interfaces to keep, people thinking.
And this is about high school students or about students.
I don't know what age of students it is, but I think it's relevant for coders also, because it's really easier for coders to slip into trusting, trusting the bots to let it happen.
And I, we, I am all for getting things done faster, but we need to keep people thinking about the problems and thinking about stuff.
So anyway, I have a couple of thoughts.
So I totally agree that this is a very, very, very serious danger.
I mean, I just think back to myself, if I had a magic box when I was working on a history paper and I could just say, help me with this.
I really don't remember.
I don't want to read the 30 page paper.
And if I, you know, I just, I think it can seriously stunt your, your growth as a student.
And I honestly think one of the important skills in life is just to learn, to keep going, go, you find a problem, you're like, oh, that's hard.
Or I can't figure this out.
Like a huge skill is just learning to keep trying until you do figure it out.
And if you have a magic box that gives you the answer and you're, especially if you're young, like, I mean, that's really, really rough.
Yeah.
You can use these things as really amazing tutors though.
You can say, I saw you did this.
I, that's new to me.
Why did you do this?
Let's explore this idea.
But I really doubt many students are using that.
Like once they get an answer, probably good.
Yeah.
Well, and, and like, there's ways to, you can, like I said, also, you, there's ways to use AI tools now to, that work the way they should.
Like one of like in education, you could say, here's my rubric.
here's in, it's on this, here's my ideas about what I think I should put, but I, I'm just not sure which part of the paper I should put this information.
Like the, basically using it to be, I'm stuck.
Just get me unstuck.
Don't do everything for me, but just get me unstuck.
and those are great ways to use this.
So anyway.
Indeed.
Now, final, final thought before we move off this really quick.
There's a lot of EM dashes in this.
I'm pretty sure that this entire abstract was written with AI or at least rewritten with AI.
Like just on that page, there's three or four EM dashes.
But I'm not against EM dash, but that is such a new thing that AI seemed to have brought into the mix.
Right.
But, but there's what the, what the grammarly has been used commonly forever for a long time then.
And I don't think that like that grammarly counts as an evil thing.
yeah, I don't either.
So, but, also there's way more EM dashes in, in it's like research papers than there are normal papers.
That is true.
And honestly, that's probably how they got into AI, but still.
Probably.
I'm still thinking, I'm still thinking perhaps that I got a couple of things.
some of these are a little, this is a little bit older.
It's 14 days ago.
Cause it came out right after we recorded our last episode and then we skipped a week.
So it's not that new, but it's already, this bothers me.
Just the first four, four words of this announcement.
Bother me.
AI cloud company Vercel.
Wait, no, this is a cloud company that hosts infrastructure, but they probably wanted to raise more money.
So now they're an AI cloud company, not just a cloud company, but whatever.
Let's just start from after that.
Vercel.
Vercel is breached after an employee grants an AI tool unrestricted to Google works, unrestricted access to Google workspace.
Hacker seeks $2 million for stolen data.
So some, I got to go through a little bit more, but, basically someone was using agentic AI and gave it access to the production Google workspace, which stored a bunch of data and probably wikis and stuff like that.
And then somehow they installed something bad that then used the AI, which used that access.
I don't know exactly the details, but why do I bring it up?
If you're using Vercel, you might want to rotate your keys, change your password, stuff like that.
I don't think it's a mispronation.
Vercel is seeking the money though.
Yes.
Cause they stole the data from them and they'll say, I'm going to release it to the world.
If you don't pay me, it's like a ransomware sort of thing.
Okay.
Yeah.
Okay.
Got it.
No, the M dash.
Okay.
I mean, this is the reason there's just another warning for everyone.
Like you got to be really careful with your dev machines, which are often for a lot of us also our personal computers, you know, like the whole, what was the password manager?
Not one password, not pit warden last pass last pass got hacked, not because of an AI thing, but because one of the devs had a home network, which had, a Plex server.
So they could stream their pirated stuff to their, just to watch.
Right.
But then they want to do that while they were out, while they're traveling.
So they put it on the internet.
It got hacked and then it laterally moved through their home network to get to their computer, which then got all the API keys and on and on it goes.
So anyway, just another little warning.
And if you use Vercel, maybe a double warning.
All right.
That was kind of sad.
I'll give you a good one, Brian.
Check this out.
This is very relevant.
So I want to, I went and I was just thinking like, I really want a better experience for people over at talk Python.
And I'm doing a crazy amount of stuff with transcripts.
Like I'll talk about it next week, probably.
But for weeks I've been working on making transcripts better, more with the courses than with the podcast.
But still it applies to both.
And like, it would be really nice if there was a better playback experience on the web.
Like imagine this, you come to the website, Python Bytes or talk Python, whatever.
We've got really nice search.
And I've talked about the work I've done on the Python Bytes search, which I think is really cool.
Some of the ways you can search and jump around, but maybe you find something interesting from 200 episodes ago.
Maybe you could get that on your podcast player, but you've got to like scroll back and like, how, you know, does your player cut off episodes older?
And like, it's just not great.
You might just want to watch it on the, listen to it on the web, right?
Yeah.
So you search for it, you click, you start going.
And maybe you could have a better experience than just the default playback, you know, audio tag that for some reason browsers think doesn't deserve much love or interest.
They're like, they're crappy.
They look like they're from, you know, real player in 95, but whatever.
So I went and I created a really nice playback experience where, let me just jump over.
I'll link to the blog post here, but come in here.
It's got nice little access to all the pieces, but it's got a player.
If you click it, it expands out with like little seek stuff around.
It shows the transcripts as it's playing, like right alongside the player.
You can like change the speed.
It's got hotkeys, all sorts.
And that's slick.
Oh yeah.
And thanks for doing the speed thing too, because I'd never listened at 1x.
Yeah.
So Python bytes go over here.
I've got the same deal.
I just didn't write a blog post about it because I did talk Python first, but look at that.
Oh, very cool.
Isn't that nice?
So people out there listening, if you're like, I'm just kind of exploring our content.
I mean, we've got a lot of years.
How many years, what was our first episode?
Let me just look really quick, Brian.
What was our very first episode?
It was 2016.
That's 10 years of content.
Yeah.
We've got a great search engine and transcripts on top of that.
And so if you're exploring that, you know, just use the player.
I think it's really, really cool.
We've been doing this for 10 years almost.
I know.
Damn, you're old.
Dude, weird how like some people can get old and others in the same time frame just don't, right, Brian?
Yeah.
Well, I guess.
So you'll, this is funny because if you're watching this, you'll know it, that I'm the one with gray hair, not Michael.
But you got more hair.
So I think it evens out.
So thank you.
Pat says last pass reminds me of as I was stumbled on.
Okay.
A couple more things real quick.
A combination of stuff in this last item.
I both want to give a little bit, a little bit of sympathy to GitHub and then also kind of bash on him a little bit.
So GitHub has been having.
As we do, you know.
As I think it's fair.
Like, isn't that balanced?
Yeah.
I think you just got to say if there's two sides, you got to present them both equally.
But there's, there's a little bit of nuance here.
So I don't know if you've noticed, but GitHub has been a little janky lately and not in just the GitHub actions, which have been taking a lot of heat, but just uptime at all.
Like I couldn't, I couldn't search the other day a little while before then, like issues were not accessible.
I didn't experience this, but people had their pull requests just disappear.
How frustrating would that be to do some work, submit a pull request and it just goes into the ether.
You're like, are you serious?
So here's the supportive angle.
They, they did this, this post over on the GitHub blog called an update on GitHub availability.
They have a graph that says things are hard for us.
We're trying.
They're doing a couple of things.
I believe they're reworking GitHub from being a monolith into being a bunch of microservices.
And I usually hate on microservices, but something like GitHub with all these different moving parts and different levels of traffic and load on them seems like you might want to, well,
maybe we should just scale up the issues a bit, like a ton, but not so much just listing the repos or whatever.
So apparently they're going through, they're like, oh, we need something like 10 X more capacity than we had a couple of years ago.
And during that time, they're like, actually, no, maybe 30 X more.
So it's a lot.
And if you look at the graphs, if you look at the graphs, they are nothing but like nearly vertical in the amount of traffic and new repos and commits.
And one of the main drivers of this is people, especially a lot of new people to programming who were not programmers are like, hey, Claude, create me a project.
Where do I save my project?
Oh, you put it on GitHub.
You know what I mean?
And so just the amount of traffic amplified by AI to GitHub is over the top.
All right.
So that explains- You know, maybe if we could charge like 50, if they charge like 50 cents a month, just something small, just, but anything like a dime a month, a lot of that would go away.
That's really interesting.
I would totally pay a dime a month.
I think I pay $30 a month to get up.
I wouldn't mind paying 30 and 10, 30 point, $30, 10 cents.
Wouldn't make a difference.
Anyway, no, I think that's a very interesting point, actually.
Okay.
So there's that.
This is GitHub's response.
Did you know that there's a missing GitHub status page?
Yes, there is.
If you go back to the previous one, somewhere did they talk about their uptime?
How could it exist if it's missing?
So is there a status?
Yeah.
So if you go to GitHub status page, it says, oh, Git operations are up, up, up.
Web hooks are up, up, up.
And it talks about like, it doesn't aggregate it, but it's like 99.5 sort of uptime.
But then there's another page, which ironically is hosted on GitHub.io.
I love it.
It's like its own thing.
And it basically does other types of checks.
And it's like, you know, 84% uptime.
That is actually pretty abysmal.
Yeah.
And it just has graphs.
And it actually breaks out pull requests and all these things.
And here you look and you see kind of similar numbers.
It's like the Git operations are this.
Web hooks are this.
But I think it says, if any of these are down, then you don't call it up.
You know what I mean?
Whereas the other one goes, if some of it is up, it's up.
Not all of it.
I mean, you don't like issues right now, do you?
I don't know exactly the breakdown there.
But I just thought this missing GitHub status page was really interesting.
Yeah.
They should do better.
I mean, I know that a lot of us are using it for free.
But also, we've paid for it with all of our intellectual property.
Yeah, exactly.
I mean, that's...
And attention, right?
The reason that there's not a mass exodus to something new or shinier is because this is where most of the people are.
I know there is something of an exodus, but not a mass exodus, right?
Yeah.
You get benefits from being on GitHub.
Okay.
I think all of these conversations about these AI things and stuff and others perfectly lead into this joke.
And this is probably one of my favorite jokes.
Okay.
At least of the year.
Have you looked at it yet?
No.
Okay.
Perfect.
Okay.
So I found this on X.
And I'm programming humor.
I guess it could also be on Reddit.
Like they broadcast that in multiple places.
So this is like two different perspectives from society.
And it's talking about Copilot, but it could be ChatGPT.
It could be Claude, whatever.
Friends outside of tech.
Lol, Copilot is dumb.
Friends in tech.
I just bought iodine tablets.
I have made an offer on land upstate.
My supplies of antibiotics and potable water are sufficient, but I need to set up hydroponics to make it through the first few years.
Did that just perfectly sum it up?
Yeah.
It's like, this is a dumb thing.
Look, it made this thing longer.
We're like, I'm almost done stockpiling.
We're ready to build the bunker.
I know what is coming.
I can see it.
It's so bad.
Yeah.
I'm, I've just like, I've just, I know that I'm dependent on society.
If society collapses, just, I hope I'm one of the first to get hit because I don't want to live through an apocalypse.
I really don't either.
I'm not a survivalist.
So, well, stock up on your, iodine tablets and your potable water.
Oh my God.
It's so bad.
Well, so I've got, I've got a friend that like, they've got like a group of friends that have a place like in Southern Oregon that they, they know they can hole up in and stuff.
If anything happens.
And I said, oh, okay.
So, so do you make sure that you always have a full tank of gas?
So if anything happens, you can make it there.
Oh no.
Well, how are you going to get there?
Are you going to walk to Southern Oregon?
Anyway.
So.
Yeah.
Good point.
There's a lot of moving pieces and the one you didn't see coming might be the one that takes you.
I hope he doesn't listen to this, this podcast, but I hope everybody else does.
Yes, exactly.
Well, everyone, hope your supplies are ready and thank you for listening.
Thank you.
Bye.
Thanks everybody.
Bye.