And corporate shops have rules for a reason. And what you're advocating would in many places be seen as grounds for not just dismissal, but prosecution.
Exactly. If you're developing stuff for your own amusement, then deployment to a dozen systems running mission critical stuff is never going to be a problem.
In my case it is -- which means I have to look closely at whether I absolutely need a module, or whether I can get by with something a little less 'jazzy'. This week's query was about using WWW::Mechanize -- that module isn't installed on the system I'm developing for, but LWP::UserAgent (which Mech uses) is present, so that decision is made for me.
If you look at it from the IT guy's perspective, installing a module is no easy task: the latest version of X might mean you have to upgrade Y, which has always worked fine, and of course that means you need to also update Z and W .. and pretty soon, subtle problems start to turn up. And I ran into a 'version' problem recently, where an older version of Mech worked fine, but the newer one, on a different platform, didn't.
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||