I wasn't in attendance but have watched many of the presentations and read quite a few accounts from those who were there and it seems like the implementation are coming to quite a crossroads.<p>Those interested in doing anything "serious" seem to be doing it on jruby. Real threading seems to be a much requested/needed feature for many Ruby projects, but Matz has indicated quite clearly that he is not interested in removing the Global Interpreter Lock (GIL) from MRI ruby. Which is fine, as his he doesn't want the hard threading problems to be exposed to ruby coders.<p>Its kind of a shame that the jruby guys aren't a bigger part of the conversation on new features and the future of the language. But it is quite understandable when you look at the way ruby has been used in the past, and the direction that people are taking it in the future.