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 djberg96 (2603) on 2002.07.28 19:56 (#11133) Journal
    An example and a metaphor: Why are there comments on use.perl journals? Because Perl people can't just read what other people have been up to. No, they need to jump up and have their say. They've got to yak. They need to be heard. That's the self-centered thing coming out again. Perl is full of guys in the second row. Full of them.

    What's he talking about here? I make comments on use.perl for the same reason that I write my name in the toilet water when I'm urinating - I'm bored and I don't have a life. Reading journals is much like a usenet debate - a vaste conspiracy to waste time.

    It's a sad state in any technical community when I feel I can't disagree with people on technical issues because of political pressure. There are a lot of things I think the Perl 6 and Parrot efforts are doing wrong.

    If you don't like Perl 6, do what I did and switch to another language. Ruby is a small and young community. If you want to be heard, at this point in its life, you are almost guaranteed to be heard. Ruby 2.0 is still on the drawing board, too.

    • I found the comment on comments a bit odd also. If anything, it seems that enabling comments on journal entries is a sign of willingness to give others a say, which hardly implies arrogance. I suppose one could argue that it's arrogant to think anyone will want to comment on your entries, but surely that line's been crossed when you decide to put up a journal in the first place.