Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I think (part of) the solution is something that came up in the hallways of YAPC::EU a couple of times: de-core most of the modules and dual-life everything that can feasibly be.

    Now it just needs to happen…

    • A net result would be that even more people would be less willing to use some modules. All too often, we encounter the restriction that a solution may not contain any non-core modules...
      • There are already many vendors who slice and dice the Perl package. There’s no real guarantee that a module will be there even if it’s “in core” anyway. We would just be blessing the de-facto situation. Hopefully an insistence on code modules only would then become untenable for enough people that maybe someone would finally find motivation for a good module bundling solution.

        As for the places which would still insist that only core modules be used, well, I don’t think we can

        • Awesome! I'm stupid for trying to make life easy for the rsnapshot users!
          • You are making no sense whatsoever.

            • You said:

              As for the places which would still insist that only core modules be used, well, I don’t think we can protect stupid people from themselves

              Rsnapshot doesn't require any non-core modules, and so has had to reinvent various wheels. Which, I guess, makes me, the current maintainer, stupid.

              What doesn't make sense is removing stuff from the perl 5 core distribution. Although I live in hope that perl 6 will be slim and sylph-like, with only those modules included which are required to easily

              • When I say “stupid”, I mean workplaces that could easily install modules but refuse. Writing what’s effectively shrink-wrap software in Perl (ie. rsnapshot has to run on any number of machines, none of which you have any control over) is a very different situation.

                However, even in your case, I don’t know that trimming down the core would be a problem. Are you better served working against a) a large but insufficient core, reinventing various wheels as needed, or b) a minimal core and a good tool to bundle modules into your app? (It might be that we already have such a tool – PAR. But I haven’t used it, and I don’t often hear enthusiastic praises for it, so I don’t know whether it’s good enough to consider the problem solved.)

                Of course, module bundling doesn’t require a minimal core, so my question might seem like a false dilemma. Point is, though: given good module bundling, is the size of the core any concern anyway? Also, don’t forget that vendors/distributors already slice and dice their Perl packages, so you can’t always even on the core. Given that, wouldn’t a good module bundling tool in fact be a better approach than relying on the core?