Which modules do you "allow" yourself to use for production?

Abigail abigail at abigail.be
Mon Jul 22 21:05:10 BST 2013

On Mon, Jul 22, 2013 at 07:45:28PM +0100, Pierre M wrote:
> As i was asking for advice in a previous email, Dirk Koopman wrote:
> "Use the lowest impact perl from the beginning (that probably means
> avoiding Moose, Catapole et al)."
> I understand that this means: "avoid modules with lots of dependencies". Is
> that right? I thought Moose only slowed things down at compile time, am i
> wrong?
> What is the negative impact of using it for a web-app?

Well, it's all software.

But seriously, use whatever work for your situation. Every module gives you
some benefits (using the labour of someone else), and some drawbacks
(dependencies, loss of performance/flexibility because the module wasn't
tailored to your setup, etc). 

It all depends on what your needs are. For a typical startup, there is the
race to profit: you got to make money before your funding runs out. Which
modules you're willing to use then are different then when you're already
established, and have to deal with hundreds of millions of pageviews a day.
And if you're somewhere in between, you'll make different decisions.

> Until now i've been working on a personal project, using everything that i
> fancied. Would (any of) you advise not to use any of these in production
> code?

Without having a good knowledge of your environment, I can't say.


More information about the london.pm mailing list