we are talking about advocacy, so why not promoting mod_perl in any way if it is possible and doesn't hurt anyone? I also think that it would be a good idea to set an HTTP header by default which announces mod_perl.
The winners are those who created bad but simple programs, simple programming languages like Visual Basic or PHP, with many bugs, but if they are successfully, then they can afford to improve them, to repair the bugs, and in time they become good programs with a big success. For mod_perl could be more simple to have more users, because it is a good Apache module using a very good programming language, and it just need to be made more simple to use by a beginner in programming. Teddy From: "Randal L. Schwartz" <merlyn@stonehenge.com> Adam> The people that are actually using mod_perl to any real degree > Adam> probably don't have it in their servers headers (as you said > Adam> before Perrin). > > I was just interviewed for a magazine, and this was a topic... "Isn't > PHP taking over for Perl?". > > So, while you and I may agree that this is a useless topic, the > problem is that the pundits quote each other, and they all quote the > useless statistic (mod_php is everywhere, mod_perl is dead), and so > the plebes start believing it and blogging it, and pretty soon, it > becomes a fact. A useless fact, and incorrect "fact", but a harmful > fact nonetheless. > > Harmful, in that when a PHB reads "Perl is dead, PHP roxors!" as > stated by otherwise knowlegable sources, we lose another opportunity > for a Perl design win. Yes, in an ideal world, it's not the PHBs that > pick the technology, but very few of us seem to live in an ideal > world. > > Perhaps if mod_perl announced itself by default, but a simple > directive turned it off? Then at least the statistics for it would be > in the same meaningless camp as mod_php. :) >
