Ken Jin

Most-linked posts?

1. A Plan for 5-10%* Faster Free-Threaded JIT by Python 3.16
   7 people · 9 mentions · first linked 2025-11-09
2. Reflections on 2 years of CPython's JIT Compiler
   3 people · 3 mentions · first linked 2025-07-05
3. Python 3.15's JIT is now back on track
   2 people · 2 mentions · first linked 2026-03-17

What Hacker News says?

1. kenjin4096 · 2025-03-10

   Hello. I'm the author of the PR that landed the tail-calling interpreter in CPython. First, I want to say thank you to Nelson for spending almost a month to get to the root of this issue. Secondly, I want to say I'm extremely embarrassed and sorry that I made such a huge oversight. I, and probably the rest of the CPython team did not expect the compiler we were using for the baseline to have that bug. I posted an ap…

   Comment linking /posts/apology-tail-call.html

   on “Performance of the Python 3.14 tail-call interpreter”
2. bratao · 2025-07-05

   Submitted Reflections on 2 years of CPython's JIT Compiler as a story · 79 points

   HN discussion
3. Qem · 2025-12-23

   There's some nice improvements expected by 3.16. See https://fidget-spinner.github.io/posts/faster-jit-plan.html

   Comment linking /posts/faster-jit-plan.html

   on “What's New in Python 3.15”
4. g0xA52A2A · 2025-11-09

   Submitted A Plan for 5-10%* Faster Free-Threaded JIT by Python 3.16 as a story · 16 points

   HN discussion
5. Calavar · 2025-12-25

   Because Ruby is just a better thought out language than Python is. It had a sane package management story 15 years before Python. It doesn't rely on weird hacks like exception throwing for iterator control flow. It doesn't have nearly as many warts and footguns on basic operations (for example, in Python csv.writer(file).writerows(rows) is broken unless you remembered to set the newline mode on the file; in Ruby fil…

   Comment linking /posts/jit-reflections.html

   on “Ruby 4.0.0 Released”
6. lumpa · 2025-12-25

   Submitted Python 3.15's interpreter for Windows should be 15% faster as a story · 9 points

   HN discussion
7. Qem · 2026-06-06

   > For that reason, the Steering Council is formally requesting a Standards Track PEP be authored that the community can discuss and the Steering Council can formally accept (or reject), making the case for the JIT as a supported, non-experimental part of CPython: its guarantees, its maintenance commitments, and its impact on redistributors. I didn't notice the current PEP was a provisional one. Hope the new one gets…

   Comment linking /posts/jit-on-track.html

   on “Python JIT project was asked to pause development”
8. signa11 · 2025-11-10

   Submitted A Plan for 5-10%* Faster Free-Threaded JIT by Python 3.16 as a story · 8 points

   HN discussion
9. kenjin4096 · 2026-03-18

   > I've never seen where the high level discussions were happening Thanks for your interest. This is something we could improve on. We were supposed to document the JIT better in 3.15, but right now we're crunching for the 3.15 release. I'll try to get to updating the docs soon if there's enough interest. PEP 744 does not document the new frontend. I wrote a somewhat high-level overview here in a previous blog post h…

   Comment linking /posts/faster-jit-plan.html

   on “Python 3.15's JIT is now back on track”
10. todsacerdoti · 2025-07-05

    Submitted Reflections on 2 years of CPython's JIT Compiler: The good, the bad, the ugly as a story · 6 points

    HN discussion
11. rslashuser · 2026-03-17

    I'm curious is the JIT developers could mention any Python features that prevent promising JIT features. An earlier Ken Jin blog [1], mentions how __del__ complicates reference counting optimization. There is a story that Python is harder to optimize than, say, Typescript, with Python flexibility and the C API getting mentioned. Maybe, if the list of troublesome Python features was out there, programmers could know…

    Comment linking /posts/faster-jit-plan.html

    on “Python 3.15's JIT is now back on track”
12. rbanffy · 2025-11-13

    Submitted A Plan for 5-10%* Faster Free-Threaded JIT by Python 3.16 – Ken Jin as a story · 5 points

    HN discussion
13. kenjin4096 · 2026-03-14

    I implemented most of the tracing JIT frontend in Python 3.15, with help from Mark to clean up and fix my code. I also coordinated some of the community JIT optimizer effort in Python 3.15 (note: NOT the code generator/DSL/infra, that's Mark, Diego, Brandt and Savannah). So I think I'm able to answer this. I can't speak for everyone on the team, but I did try the lazy basic block versioning in YJIT in a fork of CPyt…

    Comment linking /posts/faster-jit-plan.html

    on “Python: The Optimization Ladder”
14. lumpa · 2025-11-11

    Submitted A Plan for 5-10%* Faster Free-Threaded JIT by Python 3.16 as a story · 3 points

    HN discussion
15. rbanffy · 2026-07-15

    Submitted Python 3.15's Ultra-Low Overhead Interpreter Profiling Mode – Ken Jin's Blog as a story · 2 points

    HN discussion
16. guidoiaquinti · 2026-03-17

    Submitted Python 3.15's JIT is now back on track as a story · 2 points

    HN discussion
17. Qem · 2025-12-12

    Submitted A Plan for 5-10%* Faster Free-Threaded JIT by Python 3.16 as a story · 2 points

    HN discussion
18. rbanffy · 2025-11-17

    Submitted A Plan for 5-10%* Faster Free-Threaded JIT by Python 3.16 – Ken Jin as a story · 1 points

    HN discussion

Search all of HN for fidget-spinner.github.io