Hacker News Reader

On the other hand Rubinius implements native threads, which means for parallelizable workloads you get a potentially equivalent performance gain to the regression you are talking about. Currently the only way you can get this is JRuby (which of course comes with own its own JVM pros/cons).

I'm not using rubinius yet either, but I think there is already a compelling case to take a serious look at it.

View on HN

That's also what I was thinking but I'm a little wary of using something in production which I don't use in day by day development and I run tests against it only a few times. It seems a recipe for letting bugs slip into deploys.

By the way, I googled a little and removing simplecov shaved a couple of minutes out of the rake spec times. Still too slow and very inconvenient, even if I can still use simplecov with MRI thanks to conditionals like if RUBY_ENGINE == "ruby" ... end

"native thread" is just buzz word if the implementation cannot boot rails. On the other hand, if you don't feel like to use real multithread now, it's unlikely you need it in the future.

Reply on news.ycombinator.com