> > 1. Why is PHP so popular, with such an active user community? I think at the first look it is easier to install and use. You will get more quickly a first result and if you are a newbie your aren't able to see the limits of PHP. Also, as Axel said, PHP is available for free at most ISP, while mod_perl/Embperl isn't.
> Is there > anything in Embperl actually inhibiting its wider use? > > 2. With Embperl 2 on the horizon, is now a good time to look at how we > can improve the profile of Embperl (evangelism mode), and what's the > best way to go about that? Where are the gaps, what are we missing? > Any ideas are welcome! > 3. Is the fact that Perl has a whole slew of alternative templating > systems similar to Embperl (e.g. HTML::Mason, HTML::Template, > Apache::ASP, etc.) detrimental? Is there any way we can do about > this? (I imagine they're unlikely to all merge anytime soon!) > Embperl was the first of the more commonly used templating modules. When Mason, ASP etc. come into play I have tried to convince the authors to put the power together and make one great module. Nobody ever wanted to do this. Everybody loves it's own solution. At some point I gave up and continue to work on my solutions any ideas. So now we have a bunch of (good) templating solutions for Perl, but this makes it even harder for everybody new to Perl. In PHP you install PHP and you are done, with Perl you have to first decide which solution you use. This is an advatage for an expert, but an great disadvatage for any newbie. I don't think this will every change. One good thing in this siutation is the templating module comparsions Perrin wrote (http://www.perl.com/pub/a/2001/08/21/templating.html). I think this articel should be updated to reflect the new feature of Embperl 2.0 (I think it's also somewhere on perl.apache.org, but I didn't found it yet) > > What I was wondering was whether it might make sense to provide a > > good set of migration tools so that PHP users could move to Embperl. I don't think that at the moment there are so many people to would like to move from PHP to Perl :-( > > My feeling would be that this only makes sense if people feel that > the lack of an easy PHP->Embperl migration path is a significant > impediment to others using Embperl. I'm more inclined to think we > should be putting our effort into promoting Embperl itself - Yes, I totaly agree. It would be first necessary to show how powerfull Embperl is, so people would like to make this move. > documenting and demonstrating what we can do with all Gerald's shiny > new features, building and releasing libraries and toolkits and > entire systems built on top of Embperl (epl-nuke anyone?). Maybe we need > a showcase Embperl community site as well? > I have started a new website for Embperl. The old "design" at perl.apache.org/embperl isn't really something to catch people. The new site, will also contain a section where you can add links to publications, example etc. This could be a start. (In case you are curious, look at /eg/web inside of Embperl-2.0b6 to see what I have already done, but be warned it's not ready yet. You may also need to change path manualy in eg/web/config.pl and create a mysql database named embperl). My plan is to make the new Embperl site an example for all the nice features of Embperl 2.0, so people can more easly see the possibilities. More example code would be surely helpfull. Also writing articles about Embperl will help to make it known to the world and of course I have to write better documentation for all the new feature, so people even get a chance to see the possibilities. Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 ------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
