4 ms·
MRI is using RubySpec (RSpec is something different). http://rubyci.org/ http://rubyci.org/ The issue is more complex than Brian puts it. https://lobste.rs/s
by Argorak 12y ago
MRI is using RubySpec (RSpec is something different).
http://rubyci.org/ http://rubyci.org/
The issue is more complex than Brian puts it.
https://lobste.rs/s/oozjtg/matz_s_ruby_developers_don_t_use_rubyspec_and_it_s_hurting_ruby/comments/z17jc5#c_z17jc5 https://lobste.rs/s/oozjtg/matz_s_ruby_developers_don_t_use_...
Also, MRI makes great improvements every version _while keeping breaking changes rather low_. Changing a running system is hard.
If jitting is what you want, JRuby is a very good option.
- YorickPeterse 12y agoAt the time of terminating RubySpec not a single MRI contributor had committed any code back to the main RubySpec repository for over a year. Sure, they might use it in terms of "run the specs" but they never contributed anything back. Besides their fork was highly outdated compared to the original repository. Besides that I don't really get the fuzz about the particular tweet mentioned. This was in regard to various small changes being made that while nice were not very significant in the grand scheme of things.
- Argorak 12y agoThat's because they decided to drop their efforts in 2013, because RubySpec broke their build. Sure, it's a political debate, but just saying they don't run it also isn't honest.