Following Up on the Python JIT

  • Is LWN the only professional media organization that covers this sort of thing? It seems like core, important news relevant to a large number of well heeled professionals, it's a little wild there's so little competition.

  • 100% or even 200% seems nice, but at least at the time when I compared with JavaScript it was 4200% faster than would have been needed. Let's not even mention go.

    At least for now it seems that Python can still only be used to call some Pascal or cuda bindings if one needs performance

  • "For native profilers and debuggers, such as perf and GDB, there is a need to unwind the stack through JIT frames, and interact with JIT frames, but "the short answer is that it's really really complicated"

    I'm homeless and broken and I just spent like 2 weeks developing low level python bytecode tracer, and it SEEMS that this gonna ruin everything.

    This is hilarious - as its my first project in like 2 years

  • What's up with PyPy lately? Anyone using it in production?

  • PyPy existed since a decade ago.

  • I feel sad and disappointed in Microsoft for letting the entire Faster CPython team go. I was a big supporter, always leaving positive comments and sharing news about their work. I'd figure the team paid for itself in goodwill alone. What a letdown, Microsoft. You ought to do better.

  • I wonder what is going on with the strange ""double quoting"".