You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Edwin Pratomo <ed...@computer.org> on 2000/07/27 09:10:12 UTC

[Fwd: mod_eprl or PHP]

Edwin Pratomo wrote:
> 
> Matt Sergeant wrote:
> >
> > On Wed, 26 Jul 2000, Denton River wrote:
> >
> > > HI list,
> > >
> > > My company is using mod_perl right now and i like it
> > > alot, but now are they wanting us to start develop in
> > > PHP i really like to stay mod_perl, so i am askin you
> > > for some help,
> > >
> > > I would really like to have something to say to my
> > > boss,
> > > like this is why i want to use mod_perl instedd of PHP
> > > so my question is "Why should i use mod_perl insted of
> > > PHP.
> > >
> > > Denton
> > >
> > > ps. we are workin alot with XML.
> >
> > Well then mod_perl (well, Perl) has much more extensive XML support right
> > now compared to PHP. I was talking to Rael Dornfest yesterday, and he's
> > moving back to Perl development after developing PHP's most significant
> > XML project (meerkat) because of the tools available under perl.
> 
> Significant point.
> The availability of perl programmers is decisive, too.
> My company started with just two mod_perl programmers, and one php
> programmer to built one HTML::Mason, and one php powered site. We
> separate the content logic and the interface by writing Perl modules and
> use Mason only for interface (html) generation. By that time, we thought
> that it was difficult to get perl programmers while it was easier to get
> a php one (in Indonesia). But the truth is that it was difficult to get
> both whose skills are practical :-)
> Then we welcome any non-perl programmers (whose interests in learning
> perl), and trained them. It doesn't take long time to transform them
> into skillful perl programmers. The result is today we have five more
> mod_perl sites, while the php site is still one!
> These three new perl programmers doesn't know much about mod_perl
> stuffs, they just need to work on the interface (HTML::Mason stuffs)
> because they can simply reuse the modules which I and my friend wrote
> for the first site.
> 
> My point here is:
> Not all perl programmers need to master the complexity of mod_perl. Put
> this task upon a small team which work on the back-end system, and let
> others who doesn't have good knowledge on mod_perl to concentrate on the
> html stuffs. Mason, or EmbPerl, or any embedded perl systems (in html)
> are good choices, and their ease is comparable to php.
> 
> Rgds,
> Edwin.
> 
> >
> > --
> > <Matt/>