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.
  • <rant>So if I wrote a poorly informed diatribe about how perl sucks so much because I can't use it for my medical imaging needs*, would it be equally valid? Why is it so awful when people spout FUD and nonsense about perl but it's fine when it's about other languages?</rant>

    What's funny is I wind up saying the same thing to Java people about Perl :-)

    (*It could be great for my hypothetical medical imaging needs, but that's beside the point.)

    • I thought the article had some valid points. The startup performance issue is a bit of a red herring (i.e. so don't use it for command line scripts then), but it's still a pain in the ass and I don't see why it has to be that way. This is what the author didn't go into - why can't Java start up quickly? If so much effort has been spent in making Java run quickly, what on earth are they doing wrong at startup time?

      The whole CLASSPATH situation is a nightmare - much worse than (say) Perl's PERL5LIB system. T
      • I didn't think the whole thing was dumb:
        • Command-line programs should have better error messages. But that's a problem with the programer, not java.
        • Startup times are slower, but you generally don't use java for unixy pipeline stringalongs where this would make a big difference.
        • It would be nice if you could put all your JAR files in a directory and use the directory as the classpath rather than specifying each JAR file. But if this was really important I can just explode all the JAR files in a directo
        • A few nits:
          It would be nice if you could put all your JAR files in a directory and use the directory as the classpath rather than specifying each JAR file.
          Java is somewhat extensible in this respect: if you don't like the classloader, write your own. That's how JAR files got integrated into the platform around Java 1.2 or so.
          Not only does jar do more (compression, so he'd have to add a 'z' to his calculations for actual operation time, but tar + gzip will still be faster), they're built for entirely different purposes -- tar is a general purpose archiving tool, jar is built for creating distributable Java libraries.
          Not quite. At the heart of it all, jar is just a java-based implementation of zip and unzip. JAR files aren't magical; they're just ZIP archives with a different suffix.