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 love mod_perl, but it's horrible. I love it because I know it well, it's very powerful. I've developed in it for years and therefor I have my own set of libraries and standard development methodologies that I have developed over the years that let me quickly write applications that are flexible and powerful. Unfortunatley that doesn't change the fact that for most people, mod_perl sucks.

    As I recently wrote in a post to the mod_perl advocacy mailing list:

    Mod_perl apps are too hard. Too hard to wri

    • Hmm, please pardon my blantness, but what have you done to make mod_perl rock?

      Too many people talk, too few people do. Most of the time when I ask for help to improve mod_perl code/tests/docs on the mod_perl list I get no offers of help.
      --

      Stas Bekman [stason.org] of

      • Sorry for not helping in the past, I haven't really been in a position to. I'll try to do more in the future. I'm trying to figure out how.

        Perl is really the only language I am good at. I can program in C but I have done it so infrequently it's a stretch for me. I've ended up doing a lot more C in the last year than I ever have before and I'm finding it slightly liberating. I might be switching from a perl-only guy to a perl/C guy. At this point, however, I'd probably get involved in the iThreads stu
        • by stas (3281) on 2004.07.09 13:25 (#32320) Homepage
          Sorry for not helping in the past, I haven't really been in a position to. I'll try to do more in the future. I'm trying to figure out how. Perl is really the only language I am good at. I can program in C but I have done it so infrequently it's a stretch for me. I've ended up doing a lot more C in the last year than I ever have before and I'm finding it slightly liberating. I might be switching from a perl-only guy to a perl/C guy. At this point, however, I'd probably get involved in the iThreads stuff before mod_perl since I think it's current implementation so horribly breaks what mod_perl is trying to do that it will make things much worse.

          You don't have to know C to make mod_perl better. there are plenty of other things that we need help with. e.g. docs and tests. Just sign up on the users and dev lists and see what needs to be done. It's not hard to figure out.

          Have you ever thought of doing one perl interpreter for each mod_perl script? Is there something that already does that? It would help with the memory separation and allow for better support for using threads. I've never wanted to do that before, is it already an option?

          You already can do that, the problem is the slow perl_clone. In any case if you wish to discuss this topic please start a thread on the users list. it's very inconvenient to use this forum and hardly anyone will see our discussion

          --

          Stas Bekman [stason.org] of