RJIT, a new JIT for Ruby
I&#x27;d definitely be more apt to have this as part of production system instead of the Rust one.<p>Rust has got to be the ugliest, most unfriendly programming language I&#x27;ve ever laid my eyes on. And I wrote Perl for 10+ years, so that&#x27;s really quite a feat of aesthetics failure.<p>Anyhow, I&#x27;m pretty impressed with the performance thus far, I like the idea of having multiple JITs available for a single-language ecosystem, regardless of how disgusting the language used to implement them. I think having competition means that there will be a race to the bottom and towards the &quot;center&quot; of general work. It&#x27;s already really cool to see how the different approaches have clear preferences of the tasks they excel at and where they fall short.<p>This is hugely valuable because it pushes Ruby forward for everybody, and will hopefully result in not only a faster Ruby for X, but a faster Ruby for everything, which is just an objectively good thing.<p>Python is in a weird spot in this arena, because it is very clearly and very strongly orienting itself to continue to dominate practical data science work, and that means the need for JITs to handle regular jobs like text munging and whatnot fall by the side in order for the latest NumPy and Jax stuff, whatever is the current hot shit in the AIverse. Ruby doesn&#x27;t suffer from that because it&#x27;s pretty solidly lodged in the web development sphere, while also having a capable presence in netsec tools, application scripting, and probably a few more areas that I&#x27;m not aware of.<p>If you&#x27;re interested in some of cutting edge Python stuff, I&#x27;d recommend taking a look at exaloop&#x2F;Codon. Codon will soon be able to output Python extensions that are compatible with Python&#x27;s setuptools, so it will soon be possible to just include some .codon files with your project, use setup.py, and have decorators that can (literally) 100x your hot loops.