pov: you're a CPU waiting for Python to run a single line of code

CPU waiting for rust code to get compiled

One day someone told me "Just don't use Python" and I've been a free man ever since.

do you understand what a CPU is? (it's the thing that runs python)

I don't understand, isn't the CPU busy running that python code? I imagine python is slow because it makes the CPU do lots of things, so the CPU is more busy than it should be for a given task.

Python's like me. It likes to take its time.

The ruby code on Github's servers after getting 275m commits a week

Is this the real thing?

@polloimperial No community note means yes!

Hahahaha It would be funny if you got community noted by the python foundation

I think about this scene from Megamind often

Facts and also great movie

Game engines written in C++ struggle when you have more than a thousand NPCs on screen. Meanwhile Python can render 100,000 NPCs at the same time: At 120 fps. Maybe it's not the language, it's the skill that's the issue. 🤪

wrong if you add two numbers somewhere a C ffi is being called

the thing i hate the least about python is the speed/idea, its the packaging and bloat and all around out-doneness by a million other things

CPU entered retirement before that line finished

the funny part is how often the cpu is right to wait. most python lines are calling into c that's already fast. the slowness you feel is interpreter overhead between the fast parts, not the work itself. python is a great conductor and a terrible instrument.

Wouldn't it be running code the interpreter and other setup code until it rubs real code

CPU waiting for me to code something 🫡

Just put n_jobs=-1

Banger

it's actually CPU waiting for random memory 99% of its operating time

python deciding what to run also runs on cpu