Luckily Ruby is a language with more than one mature and stable
independent implementation (as well as several up-and-coming
implementations). The JRuby implementation was unaffected by this, and
may gain more use as a result.
My team discovered an additional bug (besides the known segfaults that
we'd patched away) in the recommended Ruby-1.8.6 version yesterday, and
had to back off to an earlier version with added patches to fix the
My next Ruby server will run JRuby.