Re: Which modules do you allow yourself to use for production?

2013-07-28 Thread Thalhammer, Jeffrey
Lots of good advice in this thread. And the timing is especially good, since I'm bootstrapping a Perl startup at the moment (see http://stratopan.com). I would also suggest looking at Pinto (http://metacpan.org/module/Pinto) for managing your dependencies. I've used tons of CPAN modules for

Re: Which modules do you allow yourself to use for production?

2013-07-23 Thread Toddy
Once you have decided what modules you need. Don't rely on installing them all directly from CPAN. Keep the exact versions of the module you're using in either your own CPAN mirror or packaged with your self-brewed Perl to simplify consistency across all of your environments. On 22 July 2013

Re: Which modules do you allow yourself to use for production?

2013-07-23 Thread Abigail
On Mon, Jul 22, 2013 at 09:39:33PM +0100, Dirk Koopman wrote: While I reckon prototyping is useful, you should be aware that when dealing with people that have Pound note watermarks etched on their glasses, prototypes have a habit of becoming (the rump of) production code. This, IMO, is

Re: Which modules do you allow yourself to use for production?

2013-07-23 Thread Ash Berlin
On 23 Jul 2013, at 11:03, Abigail abig...@abigail.be wrote: Doing extra work now in order to save costs later is a luxury problem. Your first worry should go to actually being alive later on. When you're starting up, your resources are limited, the work that needs to be done ASAP is huge,

Re: Which modules do you allow yourself to use for production?

2013-07-23 Thread David Cantrell
On Mon, Jul 22, 2013 at 09:39:33PM +0100, Dirk Koopman wrote: And yes, I would advise against producing production code that has lots of external (CPAN) dependencies, especially if the normal path through those modules touches

Re: Which modules do you allow yourself to use for production?

2013-07-23 Thread Dirk Koopman
On 23/07/13 11:03, Abigail wrote: On Mon, Jul 22, 2013 at 09:39:33PM +0100, Dirk Koopman wrote: While I reckon prototyping is useful, you should be aware that when dealing with people that have Pound note watermarks etched on their glasses, prototypes have a habit of becoming (the rump of)

Re: Which modules do you allow yourself to use for production?

2013-07-23 Thread Abigail
On Tue, Jul 23, 2013 at 12:43:05PM +0100, Dirk Koopman wrote: On 23/07/13 11:03, Abigail wrote: On Mon, Jul 22, 2013 at 09:39:33PM +0100, Dirk Koopman wrote: While I reckon prototyping is useful, you should be aware that when dealing with people that have Pound note watermarks etched on their

Re: Which modules do you allow yourself to use for production?

2013-07-23 Thread Pierre M
Dave Hodgkinson daveh...@gmail.com wrote: Don't use system Perl. Brew your own and make it part of the app. I made a few bundles with Syntax::Collector. There's the ones that i use... - in all packages: strictures, autodie, feature, Carp, true - to change the syntax, like Method::Signatures

Re: Which modules do you allow yourself to use for production?

2013-07-23 Thread Dirk Koopman
On 23/07/13 13:22, Abigail wrote: On Tue, Jul 23, 2013 at 12:43:05PM +0100, Dirk Koopman wrote: On 23/07/13 11:03, Abigail wrote: I sometimes express myself too forcefully. I am trying to suggest that there is a balance to be struck. Further more, I believe that a successful developer does

Which modules do you allow yourself to use for production?

2013-07-22 Thread Pierre M
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

Re: Which modules do you allow yourself to use for production?

2013-07-22 Thread Jason Clifford
On Mon, 2013-07-22 at 19:45 +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). Surely you need to have an idea of the scale of the project before making

Re: Which modules do you allow yourself to use for production?

2013-07-22 Thread Abigail
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

Re: Which modules do you allow yourself to use for production?

2013-07-22 Thread Dirk Koopman
On 22/07/13 19:45, 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

Re: Which modules do you allow yourself to use for production?

2013-07-22 Thread Pierre M
Thank you, all. That's very good advice. Yup, the main thing is to make money before it runs out. Abigail, your comments to Ovid's blog post (about testing) were just what i needed to read at the time, on this subject. Summary of the ideas so far: - it depends on the size of the project - don't

Re: Which modules do you allow yourself to use for production?

2013-07-22 Thread Dave Hodgkinson
Don't use system Perl. Brew your own and make it part of the app. Sent from my iPhone On 22 Jul 2013, at 23:04, Pierre M piema...@gmail.com wrote: Thank you, all. That's very good advice. Yup, the main thing is to make money before it runs out. Abigail, your comments to Ovid's blog post