Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

There once were complaints about how had accrued bloat and feature creep, and the only way that was seen by p5p was to let it rot as the dead carcass it is and to elect a slimmer, fitter substitute into the core. The better solution would've been to cut away the cancer but neither the author nor p5p followed through on that.

So my view on such situations isn't all positive, even though I got a talk out of it and a module into the core that way. Possibly, if you were to name names, it could frustrate the unnamed frameworking author so that you get assigned maintainership. This would be the most positive alternative I see. Actually, while we're dreaming crack pipe dreams, maybe you can enter a fruitful discussion with the author (note: avoid terms like "ruined", "unnecessary") and either you realize that the author was right all the time or the author realizes that his extensions should go into a subclass.

So, I see little gain in complaining. You can always fork the module in question.

In reply to Re: How to complain about changes to a module? (And what good would it do?) by Corion
in thread How to complain about changes to a module? (And what good would it do?) by BrowserUk

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others musing on the Monastery: (4)
    As of 2021-02-28 07:29 GMT
    Find Nodes?
      Voting Booth?

      No recent polls found