>
> Perl has a high entry barrier.
yeah right ;).
perl is time-tested better for sys admin than the web. and we all know how sys admins want to use the same code for the web but it doesn't cut right. *if anything* php is 'enhanced perl' for the web, atleast that's how it started.
it's always a balance between usability and functionality. the market, the enterprise adoption etc, all tell us that php strikes a fine balance.
like going to a client meeting where i got to sell postgresql in spanish/french. i am not going to fight with them about why english is better *if* it is, i am going to give them the best they want and close the deal.
btw i got a database/language in my basement. it's the best in the world but only i can use it. but i am also not going to cry when the market doesn't adopt it.
jzs
On 6/17/07, Tom Allison <tom@xxxxxxxxxxx> wrote:
On Jun 16, 2007, at 7:51 PM, Leif B. Kristensen wrote:
>
> On Saturday 16. June 2007 23:34, Erick Papadakis wrote:
>> How much value you derive from a language
>> depends on how you use it. After playing for years with Perl, and now
>> with Python and Ruby, I think PHP is still where it's at.
>
> I too have played around with Perl and Python, and use both of them
> for
> special jobs, but I'm writing my dynamic web pages in PHP. In
> hindsight, I might have been better off writing them in Perl, but I
> was
> put off by the lousy HTML generated by the CGI module. It doesn't even
> close paragraphs. PHP doesn't have anything like the CGI.pm, but I'm
> quite content with hand coding where every single HTML tag should go.
Have you tried:
print $q->p("This is a paragraph");
recently?
Does a nice job of closing paragraphs.
