SoylentNews is people
SoylentNews
from the end-of-lifing-software-is-hard dept.
CGI.pm has been removed from the core Perl distribution. From 5.22, it is no longer included in a standard Perl installation.
There are good technical reasons for this. CGI is a dying technology. In 2015, there are far better ways to write web applications in Perl. We don't want to be seen to encourage the use of a technology which no-one should be using.
This does lead to a small problem for us though. There are plenty of web hosting providers out there who don't have particularly strong Perl support. They will advertise that they support Perl, but that's just because they know that Perl comes as a standard part of the operating system that they run on their servers. They won't do anything to change their installation in any way. Neither you nor I would use a hosting company that works like that – but plenty of people do.
The problem comes when these companies start to deploy an operating system that includes Perl 5.22. All of a sudden, those companies will stop including CGI.pm on their servers. And while we don't want to encourage people to use CGI.pm (or, indeed, the CGI protocol itself) we need to accept that there are thousands of sites out there that have been happily using software based on CGI.pm for years and the owners of these sites will at some point change hosting providers or upgrade their service plan and end up on a server that has Perl 5.22 and doesn't have CGI.pm. And their software will break.
What say you, fellow Soylents? How would you suggest "end-of-life"ing CGI.bin?
(Score: 3, Interesting) by Pino P on Saturday December 26 2015, @05:57PM
Ignoring the fact that you inserted a double negative when misquoting, CGI spawns a new process for each request. That means that there's no way to keep state internally to the program between requests
Except that's a good thing because HTTP is also stateless.
keeping all of the state in the database without any caching in the database client is probably not the right thing to do unless absolutely everything that you output comes from the database.
Just about everything you see on, say, a SoylentNews comments page comes straight from the database. And in my experience, the database server does its own caching.