Does this work put Ruby into a faster category than Python until if/when Python gets a JIT in its official implementation?
And the benchmark game is using Ruby 3.1, whereas 3.2 is significantly faster. YMMV though, it is going to depend on your use case, but we are always working on making Ruby faster, and if you run into a use case where Python is a lot faster, you can ping me on twitter @Love2Code and tell me about it. We'll take a look.
[1]: https://docs.python.org/3/whatsnew/3.11.html#whatsnew311-faster-cpythonYJIT 3.1 was eagerly allocating it's executable memory region regardless of whether it was needed or not. With the default settings that meant an extra 256M of RSS right at boot.
As mentioned in TFA that's no longer the case in 3.2, so expect this RSS number to go down by at least a good 200MB once they upgrade to 3.2.
Python 3.11.1
ruby 3.2.0 +YJIT