Maybe you just missed it for the first time. Voyager won’t restart it

It worked for me on Voyager…

I’d wager they don’t even know what you mean by “splitting an atom” and wouldn’t give a rat’s ass whether it released any energy.

The point is how arrogant this comic is. There are as many artists using AI as there are programmers. And acting like all programmers are just accepting it to send themselves “to the bread line” and that artists are somehow above that is arrogant, elitist, bullshit.

You won’t get that from artists

Bullshit. That’s so fucking elitist. Go ask all the people using midjourney to generate slop if they’re artists. They’re artists as much as vibe coders are programmers.

Kinda wish I had social media right now so I could tell DevilsPanties to go fuck themselves.

CEOs are demanding that programmers use AI, and measuring how much they use it. If they don’t use it enough, they’re in the next round of layoffs. Vibe coders are people who don’t know how to code, and probably aren’t working for a corp.

Seriously, attacking the workers? Motherfuckers.

TLDR: 3.11 is twice as fast as 3.10 at doing global name lookups, so an old speedup hack of aliasing a global function locally isn’t needed.

For example, when calling len() in a loop, going l=len, and calling l() in the loop was faster in 3.10. In 3.11, moreso in 3.13, it’s almost a wash.

However, the author says this:

Accessing functions through a module [e.g. math.sin()] or a deep attribute chain can still carry overhead. Creating a local alias or using “from module import name” continues to be effective in those situations.

But when I look at the numbers, I would say 3.13 is pretty close to making it an unnecessary optimization in general. A little subjective on how you interpret the numbers.

Great info, but this was like trying to use a recipe and reading the author’s life story to get there.

Yeah this looks to me like everyone got scammed, including the new owners.