Python 3.15’s JIT is now back on track

I'd love to understand why Python's JIT seems a lot worse than Ruby's. You'd think Ruby's would be less performant given how malleable the language is.

I'm unclear what they mean by tracing here - it sounds more like a sampling/profiling jit, rather than tracing full evaluation paths or trees, are the authors on lobsters at all?