My department is in a battle right now. We have some very por PHP
people and very pro Rails people. The php guys make a good argument
that Rails is good for new applications where we dictate the DB schema.
PHP shines where we go into an existing application, or a new one where
multiple databases or possibly legacy systems are involved. The PHP
guys basically say Rails is good for Web 2.0 type apps whereas a PHP can
do it all - including the Web 2.0 stuff (ie: CakePHP, Symfony, etc.)
The Rails guys claim that they too can do legacy system support or
mutiple databases but I’ve checked into this and its not as clean as the
PHP way of doing it. Rails certainly appears to me to want 1 db to
I can see Rails being easier to maintain and hire programmers for (PHP
talent is all around). I cannot see as many Railers out there yet.