Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • I actually have heard of and did know about most of the modules and frameworks that were suggested by many of the commenters on my blog, as do several other Bugzilla contributors. Remember, Bugzilla is written by a community, not by just me.

    When I first started to work on Bugzilla's code several years ago, it was not in a state where a project like "Use DBIx::Class and Catalyst" was a feasible project. A huge amount of cleanup was required before anybody could even see the architecture of Bugzilla.

    I'm glad
    • The module installation problem is real. Yes, Perl folks in the know are comfortable with CPAN, but it's true that many aren't.

      As have been mentioned in various threads, there are solutions to that, including "bundle them manually", PAR, automating the install off CPAN, distro packages, etc.

      This is not a language problem. Ruby and Python will both have similar issues. PHP doesn't because nobody uses any modules, they just write everything from scratch.

      Reiventing all the wheels is of course another viable op
      • Hahahaha. :-) Yeah, I hate being stuck between that divide of "reinvent all the gears, wheels, and rods" or "require more modules than anybody wants to deal with." :-)

        It's true that it's a problem in any language, though some languages have things like email handling bundled in their standard library.

        That's also one reason why PHP users require few modules--they have a ridiculously extensive standard library.

        I agree that it's better to spread the work out on libraries across the community, though. It just means that people have to install modules.

        • they have a ridiculously extensive standard library.

          Except when they don’t (because ¾ of it are optional at compile time).

          • Yeah, good point! :-) I've run into that from time to time. Thankfully I'm usually using the packaged versions that either have them all built-in or compiled as separate packages that are pretty easy to get with the packaging system of whatever distro I'm using.

            They also have PEAR, which works pretty well.