in reply to Perl and Infiltrating PHP Workplaces

How about the fact that PHP began life as a Perl templating module (a la Embperl or Template Toolkit) that got out of hand? To me, that's quite the "'Nuff said!".

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
  • Comment on Re: Perl and Infiltrating PHP Workplaces

Replies are listed 'Best First'.
Re^2: Perl and Infiltrating PHP Workplaces
by Juerd (Abbot) on May 24, 2006 at 11:14 UTC

    How about the fact that PHP began life as a Perl templating module (a la Embperl or Template Toolkit) that got out of hand? To me, that's quite the "'Nuff said!".

    I'm not sure I get it. What is said by it? I can argue both ways.

    Perl's purpose has also changed much over time. It's still a very strong string manipulator, but fares well in other areas too.

    Juerd # { site => 'juerd.nl', do_not_use => 'spamtrap', perl6_server => 'feather' }

      Whenever I work in PHP, it feels like I'm working in an odd version of TT, except that
      • I can't dip back into Perl if I want to
      • I don't control the variables available to me
      • I have to do all my work in my templates

      PHP began life as a Perl templating module and hasn't outgrown its roots. As of Perl5, neither had Perl. Perl6 will be the first time Perl will have outgrown its roots and truly blossomed as a programming language. That Perl could do as much speaks to the roots TimToady gave it.


      My criteria for good software:
      1. Does it work?
      2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
A reply falls below the community's threshold of quality. You may see it by logging in.