1. 9
  1.  

  2. 5

    This is an unsurprising outcome. The main issue of RubySpec was that it was always a political project, centered around control of who would define the actual behavior of Ruby. With RubySpec being dropped by Rubinius, it got freed up to be used by the other implementations - it’s not like they weren’t interested in RubySpec, they didn’t want to cooperate with the gatekeepers of it (for many reasons that I don’t want to discuss in details here).

    For context that I don’t want to copy, read the comments here: https://lobste.rs/s/oozjtg/matz_s_ruby_developers_don_t_use_rubyspec_and_it_s_hurting_ruby/