Ive used this module a few times, just to see how it worked. When you install it, it does a benchmark between it and CGI.pm, and the results are very much in it's favor.

Anyone who's looked at the internals of CGI will agree that it's not the most efficient perl module. It's pretty big, and wears alot of hats. But it works, and works well. CGI3 has alot to live up to if it's looking at replacing CGI.pm as the de facto CGI module on CPAN - something I am not sure it's trying to do. In fact I'm not sure what it's intended purpose is.

It's interface is similar to CGI.pm, almost identical AFAIK. I've noticed a few bugs/missing methods here and there, and emailed the Author, who is NOT Lincoln Stein, but rather a fellow named David James (see CGI3's README). He is rather proud of his module, which he should be, but bug fixes are slow to appear, it hasn't been updated on CPAN since August 24th 1999. BTW, he told me that Lincoln does the uploads in his CPAN directory, but does not develop the module.

My experience testing it has been fairly positive. Most missing methods are non-critical. Alot of the :cgi-lib stuff is gone or missing, which may be a good or bad thing depending on how much legacy code you need to maintain.

Just a few problems I have with it:

• Lincoln didn't write it. Granted others could, but I trust his work, and think he has the knowledge to ensure that the quality/security is maintained.
• Updates are rather slow. Something like CGI needs to be updated somewhat often, not once every 6 months.
• It means a new round of security fixes and updates while reviews happen on the all-new revised code.
• It was based on CGI.pm 2.60. CGI.pm is now at 2.74. Unless it's kept up to date, it won't become the successor.
• Forking CGI.pm would generally be a bad idea. CGI.pm must maintain a constant movement forward, with unified code based. If a switch is going to happen, it has to be done fully, and in one direction, forward.
• No apparent plans to move to CGI3, it "feels" like it was an experiment.

All in all, it's neat to play with, but I would not recommend using it in production code:

#Always
use CGI;
[download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.