From: Marcin Raczkowski <mailing.mr@...>
Date: 2007-10-02T01:43:48+09:00
Subject: Re: Ruby vs. PHP

> Easiest way to convince is code examples. Focus on simple tasks that
> have some reallife usage value to him (the investor). But of course
> the comparison must be fair, so dont make it too complex ;)
> 
> It would actually be nice to have a way to compare PURE php (+solutions)
> with PURE ruby (+solutions for web-tasks:
> 
>   * Post data into a "web formular" in both languages
>   * retrieve data from a mysql database
>   * run automated "comparisons" and other data manipulations
>     from a "web formular" (i.e. something for your investor
>     that makes working with it easy)
since i have background in php i can provide investor with code samples, 
but I know that ruby is better for me, problem is to convince investor 
that know nothing about programming

> Personally, I am a bit unhappy that PHP is compared to Rails so
> often ... PHP should be compared to Ruby, and then if we can,
> Ruby should improve on the area where PHP has a slight edge.
that's why I'm asking about advantages of ruby (read my post carefully) 
and in second order rails - if I'm talking about rails i should compare 
it to cakePHP or Smarty or something like that

> 
> To me, speed was NEVER a reason, and to be honest, I think
> some people really overrate the speed issue at first hand.
> At least it should be untied from OTHER reasons, such as
> the online docu part for example, where I think PHP still
> has a lead over ruby in that aspect. ;-)

Problem with online docu is that there's TONS of shity, ugly, 
exploitable code online for php and noone cares - i even saw statistics 
saying that 80% of php code have serious sql-injection vulnerabilities.


as for speed - it doesn't matter if something is 2-3 times slower then 
same thing in J2EE, it doesn't even matter if it's 10 times slower, but 
if one request to rails takes 5 seconds on modern server it DOES matter ;)