RSS | Module Info | Add a review of Object-PerlDesignPatterns

Object-PerlDesignPatterns (0.03)

I have nothing against the content itself, but I find that such a huge, monolithic document is hard to use and slow to render. If it was published in CPAN as a module, presumably it's because it should be usable within perldoc. Imagine if the whole camel book were published as a single POD file! (Well, I guess some people would prefer it that way...)

Ivan Tubert - 2004-04-13 09:27:34
Was this review helpful to you?  Yes No

Object-PerlDesignPatterns (0.03)

This documentation module is by far the best resource describing the implementation of common OOP designpatterns with perl.

The author released this module as a collection of his great wiki at http://www.perldesignpatterns.com/ which I can also recommend to every OOP interested perl programmer.

Thank you very much Scott and keep up the good work!

Roland Moriz - 2004-04-13 01:06:49
Was this review helpful to you?  Yes No

Object-PerlDesignPatterns (0.03)

This is an unusual module, since as far as I can tell
it is really a book written in pod that uses CPAN as
the publisher.

As a book, I like it. By including antipatterns,
the normal difficulties of presenting design
patterns are overcome, making for an excellent read.

The real-world perl refactoring examples are helpful.

As someone who has written both good and bad objects,
and wondered what went right or wrong,
the analysis here is insightful.

Tom Anderson - 2003-10-25 00:17:34
Was this review helpful to you?  Yes No

Object-PerlDesignPatterns (0.03)

Perl doesn't need design patterns. Design patterns are just
repeated sequences of code to work around failings of OO
systems. Most perl programmers don't even use OO to avoid
these problems. OO is over rated. If this is about design
patterns, it must be about OO, and OO is overkill. Packages
are all that is needed to write modular code. Java programmers
only use objects because the class libraries make them and there
are no other shortcuts in the language anyway. Patterns are
dumb. And design is completely pointless too. Perl programs
never get large enough that design is a problem. People
never put together teams of Perl programmers and one person
doesn't need to design their own code. Programs grow
organically. They go from small to big, cute to gnarly,
simple to twisted. When they get big and old, they die. No one
works on old code and no one uses old code. If programs expired
like eggs, people wouldn't even talk about nonesense like
software design and computer science. Those Java people must
take us Perl programers as real dunderheads to think we'd
bite on something as lame as this. -scott

Scott Walters - 2003-10-06 19:31:44
Was this review helpful to you?  Yes No

Perl.org sites : bugs | dev | history | jobs | learn | lists | use © Copyright 2002-2010 The Perl Foundation Site Information and Contacts root: (Vh | Vc)