On Fri, 2007-12-07 at 20:54 +0000, Nicholas Clark wrote: > One particular problem can be that if something you use adds a dependency > on something else you weren't previously using, so you can reach the > situation where upgrading to fix a bug will also bring in something new that > you didn't want (for valid local policy reasons).
All I'm saying is that you can't control what other people do. People experimenting with Perl 5 aren't going to stop simply because someone on the mailing list says it might make his job harder. If dependencies are a big problem for your business, learn to fix the CPAN modules, or don't depend on them at all. I get upset when arguing about this because I have never had a problem, and I depend on a metric fuckton of CPAN modules. (I'm sure a nit has come up from time to time, but I just send a patch to the author and it's fixed forever.) BTW, I like the term "failed experiment". Isn't everything a "failed experiment"? Should we remove CGI.pm from the CPAN because CGI.pm-style code is a "failed experiment" in writing web applications? Should we all stop using emacs because elisp's lack of static scope is a "failed experiment"? Should we forget about java because single inheritance is a "failed experiment"? Should we stop using Perl because TMTOWTDI is a "failed experiment"? To be clear, my point is that everyone thinks differently. What you consider failure many consider success. Regards, Jonathan Rockway
signature.asc
Description: This is a digitally signed message part