On Tue, 2004-06-08 at 12:37, Stas Bekman wrote:
> > In particular, I would say it's a mistake to think that mod_perl
> > specifically needs PR.  There is no important difference between
> > promoting mod_perl and promoting Perl in general.  That's why I think
> > this sort of thing should be pursued through The Perl Foundation, rather
> > than as some sort of separate splinter group.
> 
> I tend to partially disagree here, when you talk about web technologies, one 
> needs to choose between mod_perl, FastCGI, SpeedyCGI, mod_cgi, mod_php, 
> mod_python, etc. So promoting mod_perl is a bit different than promoting Perl. 
> Besides by promoting mod_perl you promote Perl - it's a two-edges sword.

Well, everyone seems to disagree with me about this.  Before I give up
on this point, let me say a few things:

1) Drawing distinctions between mod_perl, FastCGI, and SpeedyCGI is
mostly pointless and helps nobody.  Yes, you can do additional things
with mod_perl, principally apache 2 filters and separate access
handlers, but most people don't care about this.  The important thing is
that you can run large Perl applications very fast.  The majority of web
apps that people run on one of these environments could be moved to any
of the others with minimal changes.

2) Helping people understand that mod_perl is hugely faster than CGI is
important.  I would like to work on a good approach for this.  I have
some ideas, but they will have to wait until after YAPC.

3) I believe that mod_php, mod_python, etc. principally compete with
mod_perl based on language preference.  Promotion of Perl covers that,
and gives us vastly more resources to draw on.

I also think that separating the notions of Perl from CGI is a good
thing, but separating mod_perl from Perl is not.  There are enough
misconceptions out there already about what mod_perl is without more of
them coming from us.

- Perrin


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Reply via email to