My advice was: there is more than one way to do it and this might suit you, but if you think this one is not a good match for you, it's not a surprise because it wasn't made for beginners and you are not alone and don't have to feel obligated to force it because one data point said it was necessary.

I tried using it for awhile and it got in the way and sucked up time trying to merely replicate a multi-command, one-line alias I've been using to build and test distributions for 15 years. Maybe that's a failing on my part and I'd be happier if I'd sunk the time but I do releases rarely and it's a trivial one command, one upload, one minute process for me already. It would have cost me many hours to save maybe most of one.

you're unlikely to be able to cross all the Ts and dot all the Is

The CPAN survived a long time and grew to thousands of packages without Dist::Zilla and I doubt it's even used by a third of authors today so the comment amounts to FUD.

As to 800lb gorillas, I think they all must be weighed, har-har, carefully. Moo is not really one. DBIx::Class has no analog other than Rose::DB and it is an investment in making ongoing workflow easy which is exactly the use pattern I said Dist::Zilla made sense; I adore and recommend DBIC often but I have never once said, this is the only way to do it, and I acknowledge its shortcomings to certain kinds of power users. I would never recommend Moose at this point; it does too much that most users never care about or want to see and there are plenty of much lighter alternatives that work with uncoupled sidecars like Type::Tiny. DateTime is fantastic in its scope and attention to detail; its size and architecture makes it the worst choice in situations where a million or so dates at a time need to be processed so it's not a gimme any more than the others. This reminds me of apache as well, which I would also never recommend today despite it being the unambiguous feature king. Eschewing apache did not lead to dumbed down webservers but instead to the lean, lunch annihilating nginx which is now powering a third of the web and is the only webserver growing in usage.

In reply to Re^5: Making the CPAN/GitHub updating process painless by Your Mother
in thread Making the CPAN/GitHub updating process painless by nysus

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.