[Rails] Re: Frustrated with RoR environment splintering

[Matthew Palmer]

On Fri, Mar 31, 2006 at 02:43:04PM -0800, Seth Brundle wrote:
> With mod_perl, it was clear the community supported it as the Apache 
> solution of record for Perl, so after a year or two production engineers 
> felt safe moving in that direction. But with Ruby On Rails, the long-term 
> supported solution we can invest in is still completely unclear.

As you said yourself in another posting, some years ago, C was clearly the
community-supported programming language of choice.  Now it isn't.  Things
change.

Personally, I find the fact that Rails is completely happy supporting
several different dispatch methods quite comforting, from a survivability
point of view.  If one implementation or method goes completely down the
tubes (or is shown, suddenly, to have a major crippling flaw) I can move. 
Monocultures are bad, no matter where they are.

> And yes, there are serious reprecussions for those of us with 100,000 plus 
> lines of code to be invested in a commercial project that the platform we 
> select does not fall out of favor in 18 months.

What's this "falling out of favour" thing you keep talking about?  You don't
have to follow the herd (hurd?) on everything.  You have the source, you
apparently have the resources -- if nobody else is willing, you can keep
something that's been abandoned in maintenance mode yourself until a
suitable replacement comes along.

- Matt