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.
good article, but the C in this comparison is being called from Ruby inside a loop, it’s not as shocking as the title looks