Re: Why non-core CPAN modules can't be used in large corporate environments.

Backporting a module is likely to be faster than writing from scratch. If they can put their own code through to production, they can put code that they backported through as well. Many CPAN authors would appreciate receiving backport patches, especially well-tested ones.

Comment on Re: Why non-core CPAN modules can't be used in large corporate environments.

Replies are listed 'Best First'.
Re^2: Why non-core CPAN modules can't be used in large corporate environments. by Moron (Curate) on Dec 06, 2005 at 15:28 UTC
True, although once you get into the guts of that, it seems more appropriate to use technique from the module to fit your system - the functionality the module delivers in such situations is usually small compared with what has already been developed for the target system, so it is often easier to move Muhammed to the mountain than vice versa. -M Free your mind	[reply]
Re^3: Why non-core CPAN modules can't be used in large corporate environments. by perrin (Chancellor) on Dec 06, 2005 at 15:53 UTC
Sure, just glance at the DBI, HTML::Parser, Template Toolkit, and LWP source code, and then write your own. Have fun.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.