Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

For anyone that missed the #rubydrama in December when Brian "ended" Rubyspec, I summarized it here: https://gist.github.com/nateberkopec/11dbcf0ee7f2c08450ea

I think Brian "ending" Rubyspec might end up being the best thing he's done for it. Suddenly, as soon as he (and Rubinius) left, RubySpec is running and actively used on MRI for the first time in years, and JRuby and Opal have already swapped over to the new implementation. @eregon deserves HUGE credit for making this all happen.



Perhaps the best thing Brian ever did for RubySpec might be pouring a significant chunk of his life into starting and maintaining the project? Whatever you think of the politics, the value RubySpec has now is in large part due to him, and very likely wouldn't be around for someone else to pick up now if he hadn't invested so much into it.


Now that MRI is using it and others have picked up where he left off, the work done before is realizing its true value and is finally fulfilling the original goal. Quitting was the catalyst for change that may have never occurred otherwise. Perhaps both were very important.


It’s a decent summary, but—as someone who was part of the team back when we started the project—the goal of RubySpec was always to be the test suite and specification of the Ruby language, and for the Ruby community. It wasn’t about Rubinius, and it wasn’t an afterthought.

I’ve been out of the Rubinius (and Ruby) scene for several years now, so I can’t speak much to the rest… but unfortunately the personality clashing seems sadly familiar.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: