YJIT’s ability to improve performance by adapting to run-time behavior can increase the speed of our code in a way that dropping down to C can’t. As such, I think we should reconsider the common wisdom that “rewriting our Ruby in C” is the ideal path to performance optimization and take a serious look at “rewriting our C in Ruby” instead.
…in a very specific scenario and benchmark. And specifically in a situation where you’d extend Ruby with it.
Really not a fan of this article’s title.
yeah it is clickbaity, but I did find the article interesting