in reply to Remove CGI.pm from Perl Core?

Yay, let's remove CGI.pm so we can see more code splitting query strings manually, %ENV checking and writing out HTTP headers with print <<HEREDOCs. Also, no thought is given to providing a replacement, apparently including Plack instead is laughable, though including a subset of Pack, something like Plack::{Request,Response,Runner,Handler::CGI} would not be horrible.

Replies are listed 'Best First'.
Re^2: Remove CGI.pm from Perl Core?
by stonecolddevin (Parson) on May 28, 2013 at 18:30 UTC

    I feel like we really need to push Plack.

    It has plenty of CGI compatibility built in while promoting way better practices for free. People new to perl could easily learn on Plack and then scale up as needed without having to migrate to anything different, while allowing a broad spectrum of deployment options (FastCGI, mod_perl, Starman, etc.) CGI is heavy, old, bloated and really easily replaced by Plack in every sense in my opinion.

    Three thousand years of beautiful tradition, from Moses to Sandy Koufax, you're god damn right I'm living in the fucking past

[reply]
Re^2: Remove CGI.pm from Perl Core?
by Anonymous Monk on May 28, 2013 at 10:09 UTC
    I wholly concur with your point. CGI.pm has useful functions, but it is still 90% crud that probably should not be used (namely, the parts that output HTML. And the double procedural/OO interface).

    Core needs a module that speaks CGI but only does the bare necessities: Query strings, cookies, HTTP headers, HTML/URI escaping... and that's about it? CGI::Lite?

[reply]

      Core needs a module that speaks CGI

      Sure it doesn't ;)

      CGI::Lite?

      Nope, a module that hasn't seen an update since 2003

[reply]
        CGI::Lite?

        Nope, a module that hasn't seen an update since 2003

        It was just an example. I can see that the module is far from ideal.
[reply]

In Section Meditations