<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 10, 2012, at 4:19 PM, Jeff Bragg wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I've used Moose, and found it to be very nice, especially in comparison to old-school Perl OO. However, it usually seems like overkill for my purposes (and perhaps a violation of the KISS principle). I'm sure it has a lot to do with context; I'm generally doing systemsy, back-end stuff, and prefer to minimize my dependencies and assumptions about deployment environment.</span></blockquote><br></div><div>Then please allow me to use this opportunity to make a shameless plug for <a href="https://metacpan.org/module/Pinto">Pinto</a>.</div><div><br></div><div>IMHO, dependency avoidance is a weak excuse for doing things the hard way (and usually the wrong way). But installing stuff from the public CPAN is a lottery because you never know exactly which versions you are going to get. And if you want to lock down those versions with a private CPAN, it is a fair bit of work to manage. So dependency-phobia lives on.</div><div><br></div><div><a href="https://metacpan.org/module/Pinto">Pinto</a> aims to fix all that. Pinto makes it super easy to construct a custom repository of CPAN distributions (including your own private ones) and organically evolve your dependencies over time. So now all that "systemsy back-end stuff" can leverage anything and everything on CPAN, and you've got a solid, reproducible mechanism for building, testing, and deploying it.</div><br><div>-Jeff</div></body></html>