> and rewarding. I doubt I could do the same with a Rails app. So for
> now we're gonna stick with PHP for our public facing web applications,
> even if it is even worse for i18n/l10n/m17n applications than Ruby
> is...

An interesting performance test is to take some task and implement it in 
Rails or Nitro or IOWA or Camping or whatever, and then implement it in a 
PHP framework with equivalent functionality.

I have done some of this using CakePHP, which is a reasonably good PHP web 
development framework, and the results are interesting.  While PHP will 
benchmark faster than Ruby for isolated benchmark tasks, when one starts 
looking at frameworks with equivalent capabilities, PHP loses that 
performance advantage, at least in the limited testing that I have done so 
far.


Kirk Haines