Hello all... We're not Perl gurus by any stretch of the imagination, but the main reasons we chose to use Embperl over PHP:
- use of real, proper Perl, rather than having to learn another scripting language - Object-oriented design through Embperl::Object However, from a marketing perspective there's another key reason for using Embperl...(my main work is in marketing), your files are plain old .html files as far as the user and more importantly search engines are concerned. In our case this means that we have tens of thousands of pages in Google (for one) versus other sites who generate dynamic content using PHP who have far fewer because they're invisible to search engine spiders. Just another 'big up' for Embperl. Many thanks to Gerald and everyone else for bringing it to life and keeping it on the top of the pile. Toodle Pip Sam > -----Original Message----- > From: Gavin Carr [mailto:[EMAIL PROTECTED]] > Sent: 14 March 2002 01:59 > To: Kee Hinckley > Cc: [EMAIL PROTECTED] > Subject: Re: Taking on PHP > > > On Wed, Mar 13, 2002 at 04:18:56PM -0500, Kee Hinckley wrote: > > It sometimes scares me how popular PHP has become. Aside from not > > being thrilled with it in general (bastardized Perl with a weak > > architecture), I also don't want to be stuck using a templating > > solution that gets marginalized. (Been down that path before, for > > years I used a embedded Perl solution I wrote in 1995. It's still > > out there on at least one site.) > > I think there are a number of interesting questions involved here: > > 1. Why is PHP so popular, with such an active user community? 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? > > 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!) > > > 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. > > The new recipe system provides some of the necessary syntactic sugar. > > But most important is providing all the calls that PHP provides. > > Basically you want a Perl library that Embperl can load which > > provides a compatible API. > > > > It seems to me that with a group effort, this wouldn't be terribly > > hard, and would provide some useful routines for the Embperl (and > > other Perl-based) community. > > > > Does anyone agree? Is there interest in doing this? > > 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 - > 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? > > Thoughts? > > Cheers, > Gavin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
