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.
  • by pudge (1) on 2008.05.01 17:44 (#62536) Homepage Journal
    There are various issues involved, but most people, just as Aristotle did, come in pointing fingers and telling me how to do things and how stupid I am for not doing those things, and I just couldn't care less to explain myself in such situations. If you'd like to talk about specific things away from the assholes like Aristotle, ping me. However, most of the issues people have with speed are due to two things: hardware (which is changing very soon) and serving software (which is not changing until we move to new hardware, because I have better things to do than to implement changes to a system that is going away very soon). We implemented many of the software changes a couple of months ago on Slashdot, so we know they work, and they'll wind their way down to useperl in due course.

    • Great, this is all I wanted to hear.

      When I had to use a model to access use.perl over the weekend I wonder how on earth slashdot dealt with this problem and it seems to use some sort of optimisation and compression for the job.

      I was wondering why use.perl didn't as well, as I (possibly mistakenly) thought that use.perl was your sort of beta-testing/experimental site for Slash stuff.

      If you've got plans in the works to fix the problem, than I'm happy.
      • I (possibly mistakenly) thought that use.perl was your sort of beta-testing/experimental site for Slash stuff.

        No, that's correct, but in this case, we had some changes and the urgency of fixing and scale of problem dictated that we work on Slashdot directly, and as the issues are primarily not in the Slash code (though related to it), they just never got "backported," and then with the new network and hardware coming, I just didn't devote my own resources to bother doing it at all.

        I just got my cryptocard for the new network today. We'll be getting the new hardware soon. Huzzah!

        • Hi Pudge!

          First of all, let me thank you for all the work you've put into and making it what it is today. I really appreciate it and I think I speak for most of us.

          In any case, I decided to start wiki page concentrating the problems that we currently see with []. Everyone can contribute to it, even without registration. It's not meant as a "Why sucks" page, but rather as a checklist for what to improve so the site will be better.

          You can also use the attached d []