Une interview de David Heinemeier Hansson, le créateur de Ruby On Rails, sur l'avenir de Rails dans les entreprises.

http://www.infoq.com/interviews/David-Hansson

Et si vous vous demandez si rails correspond à vos besoins, il répond à la question :

What do you say to development managers, directors, and technical architects who are concerned about whether Rails is going to work for their particular needs?

I say "Try it out" It's free, it's fast, and you can pretty quickly get a feel for whether Rails is a good fit for the type of work you're doing. I think in general you can just look at the cultural leanings of your product or project, if you already have people who subscribe to Agile or if they are already interested in working in an iterative fashion, and have people who are not mortally invested in static typing, then I think that you can do just fine with Rails. On the other hand, if you have people who think of themselves as Java developers, then they are not developers in general. They are java developers, that's what they do. Or if you have very long development cycles using waterfall-ish approaches, then Rails is probably not a very god fit for you. But the fact is that is so easy and fast to find out for yourself, that there's no reason for you to outsource that decision. Put some of your guys on a vertical slice, a "Spike" if you will, for a week. Anybody anywhere can take a week out of their time, or even just a few days.