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

[rinceWind]

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.