comment on

If you have four developers who are handy with Perl, Java, C++ and SQL, surely they can achieve vastly more than four purely Java developers.
Not sure what you mean here.

Sorry , I meant each of them was quite competent in each langauge/domain. And whilst finding developers good in multiple languages is hard, my position stands that that these developers will be be better at development (as opposed to using neat features of one language) than a developer who knows one language.

You don't understand the argument. It's not an argument to pick Java over Perl. It's an argument to not keep Perl.

but they support that argument with the justification that Java can do anything Perl can - my position is that that is not a sufficient reason in itself to drop Perl

Shouting doesn't help.

I wasn't shouting, I was adding emphasis.

+++++++++++++++++
#!/usr/bin/perl
use warnings;use strict;use brain;

In reply to Re: Re: Is Java really better than Perl??? by leriksen
in thread Is Java really better than Perl??? by Roger

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks