<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 9, 2012, at 3:19 AM, Dodger 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; ">So... How about some old school perl without mooses and meeses?<br><br>Anybody out there code in... You know... Perl?</span></blockquote><br></div><div>Not here.</div><div><br></div><div>The <a href="https://metacpan.org/release/Pinto">Pinto</a> project was my first deep-dive into Moose. Now I won't do anything without it. Here's why:</div><div><br></div><div>Economy: Moose greatly reduces the amount of code I have to write and test. Less code means fewer bugs. And the remaining bugs that I do create are a lot easier to spot when the aren't swimming in a sea of getters/setters and other loosely related methods.</div><div><br></div><div>Organization: Roles, type definitions, and meta extensions each give me convenient "compartments" for my code. Each compartment is isolated, reusable, and testable. I find this much faster to write and easier to use than piling everything into traditional classes.</div><div><br></div><div>Community: The MooseX namespace has a ton of wonderful extensions. The've solved problems for me that I didn't even know I had.</div><div><br></div><div>-Jeff</div><div><br></div><div><br></div><br></body></html>