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.
  • There's no reason Perl can't be the VBA replacement.

    CPAN forms the core advantage because of it's Long Tail effect. It's not the strength of the core dependencies that is it's strength, it's the breadth of the modules.

    And that's the sort of thing that takes 5 or 10 years to really flesh out.

    I am continuously encouraging people to write CPAN modules in their obscure specialised areas, and to write internal things in the form of CPAN modules, so that later they can be moved over to CPAN easily.

    With the breadth of the CPAN behind it, we just really a truly brainlessly easy to install Windows installation of Perl, something we don't have with ActivePerl, something that installs from CPAN directly, not via some filtered PPM repository.

    See the PXPerl for what is the closest thing to this yet.

    And we need higher QA for CPAN, in fact to be the new corporate VBA we need universal testability. See the soon to be announced Perl Image Testing Architecture for that. And we need better tools for Perl... PPI and friends are slowly heading in that direction too.

    There are things happening, they are coming along, but they just aren't ready to intersect with the general Perl-using public quite yet.

    And remember, there's still more jobs for Perl skills that Python and Ruby. Making Perl sexy again is a harder problem... :/