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.

Java Straw Men 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • Swing disasters continue to give Java a bad name.

    It's not fair to blame Java for a bad library. This is a foolish criticism.

    I don't entirely agree. One of the often cited reasons for using Java in the first place are the cross platform GUI libraries (SWT being the other). This is not a third party library - it's effectively a core library, made by the Java folks for the Java folks. If it sucks, then it taints Java as a whole, and might make you regret ever using Swing in the first place.

    My main p

    • By that argument, you can criticize Perl because, let's face it, though CGI.pm is incredibly useful and recommended, both the code and the interface leaves much to be desired (as Lincoln Stein readily admits.) There are plenty of other "core" modules -- made by the Perl folks for the Perl folks -- against which one could make a similar criticism. Whether or not these libraries are well designed has nothing to do with whether or not Perl is well designed.

      I do agree with your comments about the "Java ment

      • Re:On Java (Score:2)

        by djberg96 (2603) on 2004.08.24 23:29 (#33663) Journal
        By that argument, you can criticize Perl because, let's face it, though CGI.pm is incredibly useful and recommended, both the code and the interface leaves much to be desired (as Lincoln Stein readily admits.) There are plenty of other "core" modules -- made by the Perl folks for the Perl folks -- against which one could make a similar criticism. Whether or not these libraries are well designed has nothing to do with whether or not Perl is well designed.
        If CGI.pm had sucked as badly as Swing supposedly does, then I think you *would* have seen a lot more "Perl sucks" out there than you did. As it is, CGI.pm is tolerable and was probably better than anything else that was around in, say, 1996 (though I'm guessing).

        This is mostly a psychological distinction (which is why I said I don't entirely agree, but I don't entirely disagree, either). I don't associate CGI as strongly with Perl as I do Swing with Java. I'm trying to figure out, as I write this, why this is. I have some ideas but it's hard putting them into words. Perhaps it's because the Java folks, and Sun in general, hype their libraries so much that Java the language and the Java libraries are inexorably intertwined in many people's minds. Whereas any fool can write their own CGI module if they don't like the one that's out there. Perhaps this ties back into open source some way.

        Well, I'm rambling now. Time for bed. :)

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.