I also have a hard time choking down some of the dependency lists for things I like but many CPAN authors have been taking a lot of responsibility for making sure their code passes tests and won't jam up a long list of stuff. I'm really impressed with it. Ultimately, it also seems exactly the right course. Should Catalyst, for example, duplicate the snippets it uses from 50 other modules just to have a self-contained release? No, (exact) duplication is a great evil in this stuff. It should be in its place with its changes, bugs, expert owners, etc.

On the Linux dist front; they are very convenient but I have seen them used repeatedly at $work as an excuse to not fix bugs and do without features for a year or more after they become available. I know tracking builds and installations ad hoc is difficult but I really dislike the way dists play out in the real world. They move the burden from the sysadmin to the hacker. And maybe that right there sums up why I'd keep CPAN/Perl chugging along as it is. It only seems to be improving and it's driven by peers, not anyone up or down the chain.

In reply to Re: Modern Perl Programming Highs and Lows by Your Mother
in thread Modern Perl Programming Highs and Lows by derby

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.