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.
  • This woke me up, just as it was nap time.

    Reading computer language development as an evolutionary issue is interesting.

    I think although the analogy of a business (Sun) and a computer language (perl) is an okay, even good, analogy, a business organization has more in common with a biological organism than a language, and a language has more in common with a religion than a business.

    Although running a business requires winning hearts and minds and using the language involves programmers tapping at keyboards,
    • Interesting thoughts, all.

      I'm interested in the statement that is perl not a contender in Web-2.0. I thought there was lots of CPAN stuff that could be considered Web-2.0

      If they knew about it.

      Here's a soul crushing exercise. Go to your favorite popular web 2.0 style search site, Digg [] or Technorati [] or [] and type in "Perl". Look at the garbage that comes back.

      And if it were easy to install.

      Jifty and Catalyst are both awesome web frameworks able to go toe to toe with anything out there. But inst

      • I have not seen any talk in the P6 circles about "easier to install". Is that problem being dealt with as well?
        • Not to my knowledge. Parrot has a couple of features to bundle up everything into a single PBC file, and it looks like we can avoid having to require everyone to recompile their own bindings to shared libraries, but there's more to distribution and installation than having a single big blob of code.

        • Not at all, but I think it’s an orthogonal issue. Ease of installation is a toolchain problem; Perl 6 is a language, not a toolchain. However, I agree that it needs to have a toolchain that’s good enough. There has been some grunting that “we’ll make that work”, but no concrete design has happened.

          Personally, I think that’s just as well, since the Perl 5 toolchain is suboptimal anyway, and anything we do for Perl 5 will be roughly applicable to Perl 6 as well, particula

          • For now I think we urgently need to fix the Perl 5 toolchain.

            Yep, that's the idea. Fix Perl 5 and Perl 6 will follow. Worked for testing.
          • And what exactly is not "up-to-snuff" about Module::Build? (Other than compatibility problems if you try to run it in 1999.)
            • Most importantly the circular dependency issue: AFAIK we don’t have the tooling in place yet by which the CPAN client could upgrade Module::Build before running Build.PL, when a newer version is necessary.

              I also remember reading mentions of other issues I’m only vaguely aware of anymore and couldn’t list. None of them sounded unfixable, most in fact benign. I think building XS modules with Module::Build needed more polish? My understanding was that more work was needed to make it really

              • It is not a circular dependency. Module::Build builds itself just fine.

                It *is* a configure-dependency issue. The cpan clients now (I think) handle configure_requires properly, so the next release of Module::Build should seal the deal.