Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

Re: When is it better to NOT release a new module?

by rinceWind (Monsignor)
on Nov 02, 2005 at 16:47 UTC ( #504992=note: print w/replies, xml ) Need Help??

in reply to When is it better to NOT release a new module?

I think my module brings something new and useful to the problem (why else would anyone ever write a module?): It provides clarity in code, is much faster (3 to 4 times) than any other module that solves the same problem and provides a simple way to turn off parameter validation assertions for a module in mature code to get even more performance out of it.

These are your selling points. This is what you should stress in your pod, if you are going to release it as a module.

You should also present some evidence, by running benchmarks against Params::Validate and whichever other modules you are wanting to compare with.

If it's that much better, go ahead and release it. If it's comparable to an existing module, work out how you would convince others to use your code instead.


Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)

  • Comment on Re: When is it better to NOT release a new module?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://504992]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (2)
As of 2018-07-21 10:00 GMT
Find Nodes?
    Voting Booth?
    It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer?

    Results (446 votes). Check out past polls.