I think it’s not a bad idea. No features have been removed, only moved. It’s incumbent upon the developer to do a local library with tools like local::lib, perlbrew, and Carton. And that should be done anyway to control versioning, upgrades, bugs, and accidental regressions. The customer should never need to know anything about that level of the code and you can have a shiny new or version specific CGI and perl to your heart’s content. And you can always cut and paste the entire CGI.pm into your code if the other strategies are too much to to handle.

The refusal to embrace new deployment strategies is something that can enforce perception of Perl as antiquated. Move forward, you’ll find the tools afford much more than they cost.

---

---

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.