@vandys @randomgeek @codinghorror As a #Perl hacker I will never besmirch #CGI as a standard or for light-use web scripts, but a lot of sins were committed with the two.
These days the done thing is to use #PSGI and a framework like #Mojolicious or #Dancer2 in a persistent app server. You don’t have to write nearly as much code, either. https://plackperl.org
The #Plack middleware can even run your code as a CGI or #FastCGI script if you reallly want.
On this day in 2008, the #Apache Software Foundation released mod_perl 2.0.4, compatible with the December 2007 release of #Perl v5.10: https://lists.apache.org/thread/shyvjnl3dww17pdv24147vbnnwpcb64b
#ModPerl embeds a #Perl runtime in the Apache #httpd web server, hooking it into all stages of the request and response process as well as configuration file logic. Before the advent of #PSGI and #Plack in the 2010s, it was the recommended platform for persistent Perl web applications without the overhead of legacy #CGI.
@js @berkes @simon #CGI for #Perl #WebDev hasn't been a best practice since the release of the #PSGI spec and #Plack middleware in 2009. There are several very good frameworks that build on PSGI, described here for folks coming from CGI: https://metacpan.org/pod/CGI::Alternatives
The CGI module itself was removed from the core Perl distribution with v5.20 in 2014 https://perldoc.perl.org/perl5200delta#CGI-and-its-associated-CGI::-packages
For anything but the simplest single-user apps, you are permitted to point and laugh at anyone that still uses CGI.
blogsum as a Plack app - https://github.com/obfuscurity/blogsum - https://metacpan.org/pod/Plack - Patches needed due to CGI::Compile: https://metacpan.org/pod/CGI::Compile#CAVEATS
The Graffiti Express
Mark Gardner
Andrew Hewus Fresh