comment on

I think CGI is perfectly valid protocol (even if we compare with fastcgi, psgi, mod_perl). For big, real websites, if's, ofcourse, not an option.

But for testing, small sysadmin scripts/gui it's just ok.

Also I think deploy of CGI script often easier.

I have a CGI scipt, I installed 5 years ago. And I use it once a two years. Between runs and reboots it does not use cpu, memory and disk IO. What else can compete with that?

However, I think CGI.pm should be removed from core, because

1. Bad implementation

2. Perl maintainers can spend time for something more usefull

3. Indeed, it's easier to update CPAN module with security fixes, than whole perl

4. It still can be on CPAN

5. Someone can write a better replacement

6. Someone can put this replacement into core

7. Unix Distribution maintainers can release package with CGI.pm and make Perl depend on it, if they want to

In reply to Re: Remove CGI.pm from Perl Core? by vsespb
in thread Remove CGI.pm from Perl Core? by rpnoble419

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks