News for hackers. Stuff that matters.

A comment on Ruby 3.2’s YJIT is Production-Ready. Parent comment

Re:Ruby 3.2’s YJIT is Production-Ready by Alir3z4 on Tuesday January 17, 2023 @03:35PM (#34418554)
Even if GvR promotes it fully, it won't be adopted unless c extensions work out of the box.

Python without its crazy amount of extensions in c-api won't survive.

[ Parent | on HN ]
Re:Ruby 3.2’s YJIT is Production-Ready by whizzter on Tuesday January 17, 2023 @03:45PM (#34418742)
This is something that's up to the community really. The PyPy developers early on made a new FFI that is also available for CPython, sadly not entirely as easy as the classic API but completely functional and if there was a push to rewrite extensions to use that FFI (or provide dual-paths) then the gap could be bridged.
[ Parent | on HN ]
Re:Ruby 3.2’s YJIT is Production-Ready by theLiminator on Tuesday January 17, 2023 @05:39PM (#34420518)
Are you referencing https://github.com/hpyproject/hpy?

I do hope it takes off.

[ Parent | on HN ]
Re:Ruby 3.2’s YJIT is Production-Ready by v3ss0n on Wednesday January 18, 2023 @07:04PM (#34434944)
They didn't update their website often , that is the main problem of people not knowing much about PyPy . But they had made CPyext compatible and works fine with several Data-science Libs over past 2-3 years . Even anaconda have a miniconda for pypy called pypyforge where many of CPyext are building fine with it and they have same performance comapre to CPython. ( Can't make C-Extension faster since they are already C anyways.)
[ Parent | on HN ]