in reply to Re^3: Perl::Minimal -- the good, bad, and the ugly...
in thread Perl::Minimal -- the good, bad, and the ugly...

Greetings, LanX.

I too greatly dislike the "bashing" of a persons chosen Language/Operating System/{...}. Mostly because the user that chooses it, tends to feel denigrated themselves.

I felt inclined to overlook that policy in this case, as 1) it sounded kind of witty. 2) My experience leads me to believe (at least as compared to Perl) it's fairly accurate.

Honestly. In my experience, it's pretty difficult to feel confident that you can safely expose PHP in the wild. At least, unless you join the patch-of-the-month club.

As a language alone. I find many times, it's the perfect choice. I just find too many risks involved. To get into the habit of using it (out in the wild).

Speaking of "witty"; loved your JavaScript note, above. :)

All the best.

--Chris

UPDATE:

I should probably note; I'm speaking largely from a Service Provider standpoint. But I still feel it holds true for anyone running a web server on with an internet facing IP.

¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH

  • Comment on Re^4: Perl::Minimal -- the good, bad, and the ugly...

Replies are listed 'Best First'.
Re^5: Perl::Minimal -- the good, bad, and the ugly...
by RonW (Parson) on May 30, 2014 at 22:59 UTC

    Honestly. In my experience, it's pretty difficult to feel confident that you can safely expose PHP in the wild.

    ...

    I should probably note; I'm speaking largely from a Service Provider standpoint.

    Interesting you say that. A few years ago, I was commenting on how few hosting services allow Perl while PHP was nearly ubiquitous. The co-worker I was chatting claimed that Perl is too powerful and assumes the coder knows what she/he is doing, while PHP assumes the coder is an idiot. Therefore, hosting services are much more comfortable with PHP than with Perl.

[reply]
      WOOT! That's rich.

      I really don't want to take this off topic. But I'll say this much. I can tell you at any given point in time, which (PHP) apps are vulnerable, as my logs are flooded with the name of the vulnerable file name. w/o fail, they all end in .php. On the flip side; I never see a Perl extension, nor any Perl application I am familiar with -- ever.

      In the end; I'll happily grant Perl access, over PHP, any day.

      END PHP vs Perl thread.

      --Chris

      ¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH

[reply]

        On the flip side; I never see a Perl extension, nor any Perl application I am familiar with -- ever.

        I wouldn't get too carried away with the "Perl is more secure than PHP" rhetoric. We've had our own problems too. Like, you know, I don't suppose anyone here really wants to talk about suidperl.

[reply]
        "Ever"? Matt's Scripts were famous for them. I've seen a number of SQL injection attacks in Perl scripts as well.
[reply]

In Section Meditations