Re: [PHP-EVANGELISM] Another idea

> On Sat, Apr 27, 2002 at 02:43:31PM +0200, Tal Peer wrote:
>> What about writing a script in PHP, then writing scripts that does the
>> same thing in other languages such as ASP, Cold-Fusion and PERL. Then
>> posting the scripts in the site, letting people see the differences?
> OK, but then you should not write sniplets as:
> PHP:
> class Foo
> {
> 	function Bar()
> 	{
> 		return "Hello world";
> 	}
> }
>
> ASP (VB):
> class Foo
> 	function Bar()
> 		bar = "Hello world"
> 	end function
> end class
>
> Now, i hear you say that asp can't inherit. You're right about that.
> But PHP hasn't (yet) private functions/variables.
>
> But we should point out how things are done in PHP. Such as SOAP, XML,
> Caching, XSLT, etc. And then it doesn't matter how things are done in
> other languages. It's not up to the developer to make the decision
> which language is used. That's up to the project manager.
>
> Most IT Manager	aren't really into a programming language. They make
> decisions about what they hear and see. Let's say a customer want to
> create an ASP (Application Service Provider) application (Such as
> Google SOAP), An manager looks around which languages (And also looking
> what is used inside a company and what the company preferred..) can be
> used.
>
> As a Development Manager i have to advise the project and financial
> manager which language would do. I love PHP. But if an application
> replies heavily on XML and SOAP i propose to use ASP because this are
> weak points of PHP. But for a content providing systems (such as news
> feeds) and import/export programs i propose mostly PHP. It's hard to
> say when a project uses ASP or PHP. License and servers costs are
> mostly not the issue.
>
> So only showing how asp/Java/cold-fusion/.net/c/small-talk/etc/etc
> thing are done in PHP won't solve most issues. We have to show and
> proof (With writing proof of concept sniplets (or even small projects)
> that thing could also be done in PHP. It's not about how things are
> done, but if things can be done..
>
> But what you can do is making a pro/con list between asp/php, Java/php,
> etc. But it's than also important to tell the weak points about PHP..
> because not one language is perfect.

I agree with you that mangers don't care about these things, but IMHO the
site should also aim to developers who want to get into web development but
don't know which language to use.

-- 
"Boredom is our only enemy"

Tal Peer