Someone needs to take jwz aside...
dominic at thoreau-online.net
Wed Apr 20 12:21:02 BST 2011
On 20 April 2011 11:42, Zbigniew Lukasiak <zzbbyy at gmail.com> wrote:
> I generally agree that bloat happens and perhaps we should think a bit more
> about that - but I don't think there are any simple solutions.
> The alternative to having one big, but mostly universal module (like
> DateTime) is to have many small specialized modules. The problem is that
> these specialized modules usually still have huge overlap between them -
> like the many other date time modules or OO frameworks. If your project is
> complex enough you'll have many of those overlapping specialized modules
> used there, directly or indirectly - and this can cause more problem then
> standardizing on a one that would cover all the cases.
i did see the counterpoint to this a while back when putting in a
module to CPAN for $past_employer.
Not so much "huge dependency chain" as "there's more than one way to
do it" being a problem.
In this case, all I wanted in the dependencies was insist that a
system have the ability to connect via HTTPS, but there are several
modules that can provide this, but that's not the way the dependencies
Because my requirements where actually fairly light, in the end I
arbitrarily chose one and made it a requirement, but I still think
this wasn't as elegant as it could be.
Nonnullus unus commodo reddo is mihi.
More information about the london.pm