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

use Perl Log In

Log In

[ Create a new account ]

Journal of johanvdb (1872)

Friday October 11, 2002
07:18 AM

Perl is better than java! One reason why.

[ #8321 ]

When developing in Perl, yesterday evening, I noticed something that favours Perl to java. When running my application, I did the following:
perl -I ./lib -MMyApp -emain

This is similar to java:
java -cp ./lib com.stupidcompany.myapp.MyApp
(Calls the magical main method on MyApp class)

So far, so good! When I finish up my application in Perl, I can install it in the 'site_perl' directory of installed modules (using ExtUtils::MakeMaker - cross platform and standard), and then I can do:
perl -MMyApp -emain

Java, on the opposite, does not has a notion of a central class/package repository on a local machine. Instead, java app vendors deliver a long list of .jar files and such that you must include in your CLASSPATH environment variable ... in the end, you have to type up a zillion classpath entries to get a stupid app running. (Everyone who has toyed -what else can you do in java? - with XML in java knows about the classpath hell).
java -cp "~/javalibs/a.jar;b.jar;c.jar;... ad infinitum" com.stupidcompany.magicmain.MagicMain

Perl is good, it provides me with a central repository for my modules!

Regards,
Johan

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.