I think the point of the talk was that the original idea of patterns was to describe a common language for talking about issues that needed resolving, but that that has been perverted by a fixation on particular implementations of particular solutions to the general problems. It's not that we don't have the same problems to solve, just because we use Perl. But, it is often the case the that our implementations are radically different than those proposed by the patterns movement people, and many of our implementations are simpler because of Perl. Which is an ironic indication of how important the general problems are, after all why are there such clean implementations in Perl? Surely not because the general problems are unimportant.

The pity is that the patterns idea was subverted into an object only approach to implementations of the named patterns in the GoF book. This is bad not just because the particular implementations in that book -- and in other patterns movement resources -- are not applicable to Perl, but because the focus has shifted from talking about general problems to talking about particular solutions. We happen to notice this shift more, because the resulting solutions are so poorly shaped for our favorite language.

Phil

In reply to Re: MJD's "Design Patterns Aren't" by philcrow
in thread MJD's "Design Patterns Aren't" by Scott7477

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.