On Wed, May 6, 2009 at 10:42 AM, Jonathan Leto <jal...@gmail.com> wrote:
> Howdy, > > > Thanks guys for sticking up for me. I am just old-fashioned, I guess; > for > > better or for worse, I'm not interested in changing/fixing Perl itself, > just > > in finding & writing reusable code that meets my needs without adding > stuff > > that doesn't. > > Wow, I was taken aback when I read "not interested in changing/fixing > Perl itself". Ever heard of technical debt? You can feel it every time > you type "my ($self) = @_". Also, Perl 5 doesn't have OO, it has > blessed scalars. Just sayin' ;). > > If you want to maximize your code reuse, I suggest drinking the Moose > Koolaid and learning about roles [1]. Chromatic has a pretty nice > description [2] and hdp gave a nice description of them at a recent > PDX.pm [3]. There are a couple of big problems with adopting Moose or one of the similar redesigns of Perl OO. 1. Not every module you're using will be Moose-based, so if you're working on one of those, you'll need to remember to switch back and forth. It's bad enough having both (Perl's approximation of) OO and procedural calls. 2. If we bring someone new onto the team we'd have to train them not just in Perl, but in Moose as well. There are tons of books and online resources for Perl, but only Moose's own documentation for that. All the examples, code snippets, books, and howtos that people might want to use would have to be adapted to fit into a Moose framework. 3. If I am going to change languages, I'd rather switch to Ruby or Python.
