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've made a new post on my blog ( []) , trying to go into a bit more detail of why I think the Groovy/Grails versus Perl comparison has this outcome (a win for G/G). It's difficult to be really really objective in comparisons like this, and I guess none of us even try very hard. Still, I wanted to say that I have a lot of respect for the Perl community and CPAN. At the same time, I also have a lot of respect for the people who buil
    • Thanks for responding.

      I don't care if you like Groovy or Grails. If they're appropriate for your business, great. If Perl's not appropriate, that's fine too.

      I do care, very much, if you propagate myths and baseless rumors about projects I work on. Well-researched and well-reasoned discussions are fine. I don't believe you've said anything more than "I don't like Perl" and "I don't think it can work."

      I have a lot of respect for the Perl community and CPAN.

      I'm not sure you understand either one.

      You've changed your subtext from from "Sigils are HARD to READ!" to "There's more than one way to do things, and that MUST make it hard to get things done."

      I believe that's still superficial criticism. It's also wrong. The CPAN is a great example of TIMTOWTDI. If your subtext were true -- that Perl is dying because people are confused -- then the CPAN wouldn't be growing. Other languages would have bigger and better repositories and ecosystems.

      I can't name one. You can't either -- especially not in a language with a central management structure (the kind required to pull off the coup you imply Perl needs, where thousands of volunteers all receive new assignments to work on only the officially sanctioned projects).

      (Try that line on LKML sometime, for kicks.)

      Oh, and Moose [] and Mouse [] aren't competing systems either, as the official documentation in the latter link explains. As well, Moose and the standard Perl object system are compatible.

      We may take TIMTOWTDI seriously, but Perl is, by design, a very broad church. Look at the Test:: namespace on the CPAN, for example: hundreds of modules, 99% of which can all work together seamlessly in the same program. We didn't achieve this through some five-year plan from a central planning office. We achieved this the same way we achieve everything in Perl: rough consensus and iteration around working code.