They did do a lot of work towards improving ruby performance remember this post: https://blog.twitter.com/2011/building-faster-ruby-garbage-collector https://bl

They did do a lot of work towards improving ruby performance remember this post: https://blog.twitter.com/2011/building-faster-ruby-garbage-collector https://blog.twitter.com/2011/building-faster-ruby-garbage-c... I think a big issue was at the time mainstream ruby was 1.8 and upcoming versions 1.9/2 would later replace and create a minor python2/python3 type issue where many later organizations using ruby 1.8 did not upgrade to 1.9/2 not until just recently, causing a kind of stall in patches contributions to what is now 2.2 That said many of the ideas from twitters work and others is now in ruby.