From: Szabolcs Szasz <sz@...>
Date: 2002-10-15T04:13:26+09:00
Subject: Re: ruby<=>php for web scripting

"MikkelFJ" <mikkelfj-anti-spam@bigfoot.com> wrote in message news:aoesk2$l7q$1@netsrv2.spss.com...
> 
> > I've a question. Probably I will be a web programmer. They want me to
> > program in php. How can I (can I) get them to use ruby instead of php?
> > I just cannot tell them: "because ruby is more OO", they don't know
> > about programming...
> > So any ideas, links?
> 
> If it is a large project, Ruby offers increased productivity because it
> reduces code complexity.
> If the project needs wide deployment on off-the-shelf ISP's, PHP is readily
> available, Ruby is not.
> 
> Mikkel


FWIW, my impression is the same, Ruby may be more of a promise 
as yet, than a solution to some web-programming problems (especially
for ISPs who are under pressure and care more about quick profit
and low risk than nice code). Also agree with Mikkel on the code 
size thing: the bigger the project, the better Ruby may suit it than PHP.

So, Ruby necessasrily means higher risk to any manager, in terms 
of unexpected problems (perhaps related to unusal server configuration, 
performance requirements, whatever), simply because PHP has been 
tested and pressed harder in the web business than Ruby. Also, if
you get hit by a bus tomorrow, they won't easily find anybody to 
finish/maintain your Ruby code. But even bus drivers can do PHP 
today. Also, a _lot_ of ready-made frameworks, toolkits, docs. etc. 
are available for PHP. Much more than for Ruby.

But you could still try convincing them that _you_ (better yet: the 
task itself) should decide which language to use... Well, then you 
can enjoy having the full responsibility, too... ;-)

Good luck,
Sab