2 ms·

> Python and Ruby have, I think, reasonably chosen to have slower simpler implementations… ? https://shopify.engineering/yjit-just-in-time-compiler-cruby http

by igouy 5y ago

> Python and Ruby have, I think, reasonably chosen to have slower simpler implementations… ? https://shopify.engineering/yjit-just-in-time-compiler-cruby https://shopify.engineering/yjit-just-in-time-compiler-cruby

munificent 5y ago
Yes, CRuby is slowly moving towards a JIT now because performance is a major blocker for user adoption. The larger Python ecosystem has tried that a number of times too (Unladen Swallow, PyPy, etc.) It's quite difficult since both of those languages already lean heavily on C FFI and having frequent hops in and out of FFI code tends to make it harder to get the JIT fast. JITs work best when all of the code is in the host language and can be optimized and inlined together.