Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Point taken, mostly... However, I'd say that even something so nebulous as a framework should have some concise description. If it doesn't, it probably should be either broken up or put out of its misery. The name "Apache" is necessary because an "httpd" is a common, well-established chunk of software with many implementations. There's no particular feature that distinguishes Apache within its niche; while it may be better than IIS, there's no concise description of how. Therefore Apache has to be distinguished based on a label or brand.

Given Apache's brand recognition, it's not such a bad name, but if it were distributed through CPAN, it should be called "HTTP::Apache" or "HTTP::Server::Apache" or something. In some sense, CPAN's naming works because it puts function before brand, making it easy to find software to solve particular problems affecting small numbers of people, and to distribute solutions to such idiosyncratic problems. If CPAN becomes more and more about reinventing subtly-different wheels, then tags or "brands" will be required, but for it to continue to work, these should always be subordinate to the functional labels.

Personally, I'd much rather see people working to improve existing modules and solve new problems than write endless config- and argument-parsing modules, web application frameworks, or what have you. I understand the appeal, but at some point your alternate approach won't be different, better, or cleaner, but merely "other". People will choose your module for the same superficial, brand-identification reasons they choose Crest over Colgate. Your module's needing a vanity tag suggests (but doesn't necessarily entail) that you may be in this situation.


PS: Looking for something to adopt? Identify the 3-4 ordered collection (heap) modules on CPAN, choose the one that sucks least, and give it a beautiful, natural tied array interface and a screaming XS backend.

In reply to Re^6: "Vanity Tagging" on CPAN? by educated_foo
in thread "Vanity Tagging" on CPAN? by BUU

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 cooling their heels in the Monastery: (4)
    As of 2020-07-13 05:40 GMT
    Find Nodes?
      Voting Booth?

      No recent polls found