Re^2: Remove CGI.pm from Perl Core?

.... and another PHP coder is born...

If ease of deployment is the primary concern, nothing beats PHP anyway, so either someone comes up with something even easier to deploy (and maintain) than mod_php or we've already ceded that cohort.

If the alternative is people switch to (say) Ruby or Python, then they're going to have a dilly of a time realizing that none of Django, Rails, Flask, Sinatra, et al are core libraries in their respective languages either.

Nothing in core should ever be allowed to become stale and outdated.

Without a small army of volunteers, how do you turn should not into does not?

Comment on Re^2: Remove CGI.pm from Perl Core? Download Code

Replies are listed 'Best First'.
Re^3: Remove CGI.pm from Perl Core? by locked_user sundialsvc4 (Abbot) on May 28, 2013 at 13:19 UTC
If one is actually talking about getting web work done, vs. religion, then PHP does deserve some praise ... before being taken out in front of the wall at dawn, and shot. `;-)` Most of us have to admit that we have some responsibility somewhere for some big PHP monstrosity, probably written in some (equally monstrous ...) PHP version that is no longer being maintained anymore, but which remains in service (and locked in limbo) because someone on the PHP team decided to make some feature of the language “–er” in some incompatible way. Nevertheless, what they do with their tool is their concern, not Perl’s. At the end of the day, they’re all just ... tools ... and we probably use many of them, before returning, with a gentle sigh of relief (and perhaps a nip of fine cognac), to ... Perl. `:-D`

Replies are listed 'Best First'.

Re^3: Remove CGI.pm from Perl Core?
by locked_user sundialsvc4 (Abbot) on May 28, 2013 at 13:19 UTC

If one is actually talking about getting web work done, vs. religion, then PHP does deserve some praise ... before being taken out in front of the wall at dawn, and shot. ;-) Most of us have to admit that we have some responsibility somewhere for some big PHP monstrosity, probably written in some (equally monstrous ...) PHP version that is no longer being maintained anymore, but which remains in service (and locked in limbo) because someone on the PHP team decided to make some feature of the language “–er” in some incompatible way.

Nevertheless, what they do with their tool is their concern, not Perl’s. At the end of the day, they’re all just ... tools ... and we probably use many of them, before returning, with a gentle sigh of relief (and perhaps a nip of fine cognac), to ... Perl. :-D