There once were complaints about how base.pm 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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|