From: Robert Wagner <robbie.wilhelm@...>
Date: 2005-07-19T01:52:28+09:00
Subject: Re: Ruby VS PHP

2005/7/16, Dominik Schl�tter <schlu-do@gmx.net>:
> I think there's a lot of prejudice in that field. There are people
> building high-traffic websites using PHP, and I think it scales at least
> as good as "Ruby on Rails" (as you can use the same methods for
> distributing your server load). There's also commercial support
> available from Zend <http://www.zend.com/>.
> 
> And last but not least it's still much easier to find a web hoster who
> supports PHP (with database bindings etc.) than to get support for Ruby
> or even Rails. The latter is changing, though - but at least here in
> Germany there's still a long way to go.
> 
regarding webapps php is still the benchmark. why? change the script,
press reload - see the ...aehm error.. no .. changes.
i don't know why theres so much hassle with mod_ruby or fcgi. sooner
or later you will get problems with "in memory hanging classes" or
something. strange effects with "same-request-different-output". i
think it deals with the aggressive cleanup mod_php is doing between
requests so there are no problems on this side.
dry writing sourcecode for ruby/ ror is much more satisfying than php.
but testing or going productionmode with a ruby webapp - for me (with
php background) is quite hard...
how can providers sell virtual domains with mod_ruby, when you (their
customers) must be able to restart the webserver all the time?

regards,
  --robert