On Fri, 28 Sep 2012 00:32:58 +1000, Chris Angelico wrote: > On Thu, Sep 27, 2012 at 11:59 PM, Grant Edwards > <invalid@invalid.invalid> wrote: >> On 2012-09-27, Chris Angelico <ros...@gmail.com> wrote: >>> On Thu, Sep 27, 2012 at 4:01 PM, Steven D'Aprano >>> <steve+comp.lang.pyt...@pearwood.info> wrote: >>> >>>> Given how Perl has slipped in the last decade or so, that would be a >>>> step backwards for Python :-P >>> >>> LAMP usually means PHP these days. There's a lot of that around. >> >> Yea, unfortunately. What a mess of a language. I recently had to >> learn enough PHP to make some changes to a web site we had done by an >> outside contractor. PHP feels like it was designed by taking a >> half-dozen other languages, chopping them into bits and then pulling >> random features/syntax/semantics at random from the various different >> piles. Those bits where then stuck together with duct tape and bubble >> gum and called PHP... >> >> As one of the contractors who wrote some of the PHP said: "PHP is like >> the worst parts of shell, Perl, and Java all combined into one >> language!" > > I can't remember where I read it, and I definitely don't know if it's > accurate to current thinking, but the other day I found a quote > purporting to be from the creator of PHP saying that he didn't care > about memory leaks, just restart Apache periodically. It's definitely > true of most PHP scripts that they're unconcerned about resource > leakage, on the assumption that everything'll get cleared out at the end > of a page render. PHP seems to encourage sloppiness.
Fair enough, but it's the M in the LAMP stack I object to. I'd much rather have P. -- http://mail.python.org/mailman/listinfo/python-list
