in reply to Remove CGI.pm from Perl Core?

I agree with the post by chromatic (see above link) that CGI should be re-written to conform with the new Perl Best Practices.

I hope I didn't give the impression that I believe that! Any code that's currently using CGI.pm can safely continue to do so. That's fine—that backwards compatibility is important.

Personally I wouldn't recommend any new code use CGI.pm. Keeping CGI.pm in the core elevates it artificially to a recommendation in many minds, and that's not great. You're far better off using something compatible with PSGI (even Plack::Request directly, or at least Web::Simple) than CGI.pm.

Replies are listed 'Best First'.
Re^2: Remove CGI.pm from Perl Core?
by rpnoble419 (Pilgrim) on May 27, 2013 at 17:40 UTC

    I'm sorry if I misinterpreted you. Though having a modern way of using CGI is still a good idea. Sometimes we don't need the overhead of a "Framework" to get a task done. That is where I think the future of CGI may be...

[reply]
Re^2: Remove CGI.pm from Perl Core?
by Anonymous Monk on Mar 10, 2015 at 15:50 UTC
    This is a REALLY REALLY BAD IDEA!!! And please turn off the stupid warnings and get a grip. CGI is hugely important! It has already been hard telling people to use this or that version of Perl, but now you are going to create that on steroids. This is the dumbest idea I have ever heard from this community. Are you trying to self-destruct? Maybe you should try to explain to a customer who uses your software and knows nothing about Perl how to use CPAN to add modules and how to tell if they even need to. Ugggh, I am so upset over this. It is one thing to refuse bloat, and it is another to remove features. The first is good, and the second shows utter lack of understanding in software development.
[reply]

      I think it’s not a bad idea. No features have been removed, only moved. It’s incumbent upon the developer to do a local library with tools like local::lib, perlbrew, and Carton. And that should be done anyway to control versioning, upgrades, bugs, and accidental regressions. The customer should never need to know anything about that level of the code and you can have a shiny new or version specific CGI and perl to your heart’s content. And you can always cut and paste the entire CGI.pm into your code if the other strategies are too much to to handle.

      The refusal to embrace new deployment strategies is something that can enforce perception of Perl as antiquated. Move forward, you’ll find the tools afford much more than they cost.

[reply]
      > Maybe you should try to explain to a customer who uses your software and knows nothing about Perl how to use CPAN to add modules

      Most important CPAN modules are already available as ready to install packages.

      > apt-cache search  libcgi-pm-perl
perl-modules - Core Perl modules
libcgi-pm-perl - module for Common Gateway Interface applications

      [download]

      Cheers Rolf
      (addicted to the Perl Programming Language and ☆☆☆☆ :)

      PS: Je suis Charlie!

[reply]
[d/l]

In Section Meditations