From: Nathaniel Talbott <nathaniel@...>
Date: 2004-01-13T04:01:25+09:00
Subject: Re: Stability for Production? 1.6 vs 1.8?

On Jan 9, 2004, at 17:21, Derek Lewis wrote:

> What's all your thoughts on using Ruby for a production application?  
> The
> language itself (and libraries) is well suited for the project, and the
> performance is acceptable, even if some things may need to be done on 
> C.
>
> My only concern is stability.  I originally developed my rcoaster
> application on 1.6, but I've been running it on 1.8 lately, and I seem 
> to
> encounter a fairly large number of segmentation faults.  Despite that, 
> my
> gut tells me that in 6-8 months, stability will be much better.
>
> I'd just like to hear some opinions on what you think of putting my 
> eggs
> in the basket labeled "Ruby" for a production application. :)

My experience has been that Ruby is very stable so long as you don't 
link against libraries that use pthreads. All of my serious 
difficulties with using Ruby in my production application have centered 
around pthread libraries and Ruby's corresponding --enable-pthread 
directive. Even with those problems, I've found support, including 
fixes, to be excellent, and the stability has improved immeasurably in 
the past month or two. So looking at a 6-8 month timeframe, I think 
even if you need to link against pthread, stability will be fine.

My $0.02,


Nathaniel

<:((><