in reply to Using Perl vs Java with MQSeries

In your case, I would recommend Java over perl for these
reasons:

(1) Its strong typing may coerce developers to maintain
a somewhat more maintainable design than perl.

(2) Java trades away power for readability; it's easy to
write horrible Java, but it's even easier to write horrible
perl.

(3) Typical 3rd-generation logic constructs are expected to
be used in Java. There's usually only one way to do it in
Java. This leaves fewer surprises for the maintainer. That
means people who aren't as familiar with Java can't do as
much damage to the program as a perl novice to a perl script.

If you don't need perl's power, by all means, use Java!

Be warned, however: automation and data processing are fun
in perl, while in Java they can be an absolute headache.

Rob

Replies are listed 'Best First'.
Re: Re: Using Perl vs Java with MQSeries
by perrin (Chancellor) on Nov 27, 2001 at 12:17 UTC
    This is a strange post. None of the reasons you give for using Java relate to the question (MQSeries) specifically; they're just general complaints about Perl, and they border on FUD. Many of us have written large systems in Perl, and found them as maintainable as any Java code.

    There's nothing wrong with criticizing Perl and people do it here all the time. However, try to make your critiques on-topic for the question you are answering.

[reply]

In Section Seekers of Perl Wisdom