On 05/06/06, Tanner Burson <tanner.burson / gmail.com> wrote:
> On 6/5/06, Mat Schaffer <schapht / gmail.com> wrote:
> >
> > On Jun 5, 2006, at 11:22 AM, ReggW wrote:
> > > 1. No native OS threads.
> >
> > I hear this argument a lot.  I do web development, so I rarely worry
> > about threads at all.  What's the problem here that it makes so many
> > people's lists?
>
>
> From a web perspective it even has the potential for performance issues.
> Because there are no native threads, its very easy for a system call (file
> or socket handling most commonly) to block the entire Ruby process, not just
> the current ruby thread.  Thanks to the ease of IPC in Ruby it can be less
> of an issue, but is definitely something that potentially affects many
> people's views of ruby.

Worth pointing out that this is only an issue if you are using a multithreaded
webserver. It's not an issue with fastcgi dispatchers, as a blocked thread only
blocks one dispatcher.

-- 
Rasputin :: Jack of All Trades - Master of Nuns
http://number9.hellooperator.net/