Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

djberg96 (2603)

  (email not shown publicly)

Journal of djberg96 (2603)

Friday October 31, 2003
12:58 AM

Anti-PHP ammo

[ #15493 ]
Someone on #python posted this. Not sure if it's been mentioned here before, but I don't think so. Interesting read on why PHP is a PITA once you reach the "large project" stage.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I tried PHP briefly before applying for a job in PHP web shop.

    They were really sold on it and just couldn't grasp why there would be any problems. Another PHP outfit I visited a few months ago used for for shell type scripting but PHP for their sites. They thought that perl would be too hard..

    It does show that large software projects are hard and require decent programmers and a real language, not self-trained html 'programmers' and a toy language like PHP or ASP.


    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
  • I'm currently rewriting a PHP application in Perl at work. Magically appearing variables and lack of namespaces have been getting on my nerves, too.

  • Although you may only be able to pry Perl from my cold, dead hands, I've found PHP suitable for smaller apps. I'm currently writing a PHP front end for XML-RPC server. Although I think PHP leaves much to be desired, it's far from the worst web programming system I've used. That honor goes to the Lovecraftian horror know as ASP/VBScript.

    As long as strictly front-end display tasks are deligated to PHP, it's a fine system. It's when users try to encode crazy business logic in PHP that teh suck begins. Gi

  • Scoping (Score:2, Informative)

    I must say, I find it a pretty good article, but I disagree on the author's point of view on variable scoping in addition, he seems to have overlooked a few extremely bad traps.
    • As opposed to the author, I do like automatic limiting of the scope of variables to the sub (er, "function") they are in. By contrast to perl, everything that you use is a local variable, unless you explicitely say it isn't. I think that's a good thing.
    • OTOH, I hate it that every variable you create outside of a function, i
    • The piece does a good job of showing you ways the you can shoot yourself in the foot while using PHP, but I really think many of these problem can be avoided in any professional development context. By "professional development context," I mean you are running your own machine and server and aren't on a shared host. On your own box, you have control over all the settings and can make sure all the troublesome ones are turned off, the good ones are enabled, etc. Whether PHP should allow you to use "stupid" s