AG> Let me just say that this is the single biggest problem that I see
AG> with Ruby.  To my mind, native threading support is a must for a
AG> language to be widely accepted.  Ruby's internal threading support has
AG> already demonstrated how elgantly Ruby can support common threading
AG> patterns - I'd love to see the ability to transparently drop in either
AG> Ruby-thread or native thread backends into a Ruby program, without
AG> changing anything but the threading class used.

I'd also vote to put this near the top of the priority list.

thanks,
-joe