https://www.fastruby.io/blog/assets/images/RRBPerfHistory_72...
Then in 3.2, ruby released YJIT which improved median rails response time by about 100%
https://raw.githubusercontent.com/easydatawarehousing/ruby_m...
It's kind of a golden era for rubyists that stuck it out. Beautiful maintainable code that hits C performance for many tasks.
Really?
https://tomaszs2.medium.com/ruby-3-2-0-is-from-another-dimen...
here are some benchmarks from 2019 (ruby 2.5) related to string and regex operations. already certain operations were faster in ruby than C or go, particularly on longer strings.
And people definitly chose ruby because it was cool. So what you said should be applied to Ruby, not Go.