comment on

It all depends on how you use information like this...

Sure, there will be people who will (wrongly) scream See, Java SUCKS!...and to me they end up sounding as moronic as those who scream See, Perl SUCKS!.

On the other hand, if you can acquire some intelligent reasoning from messages like these, then I think you owe it to yourself as a developer and to your clients to be as well informed as possible. If I were talking to a client that was considering going the EJB route, I'd want to talk to the author of this piece and gain more detail on why it didn't work for him. Then I could say, 'that might not be the best way' and cite this developers experience. That isn't Java bashing to me, nor is it Perl advocacy. Perl might be the right tool...it might not. I guess the bottom line is to have reasons and evidence to support why you think some tool isn't the right one.

/\/\averick
perl -l -e "eval pack('h*','072796e6470272f2c5f2c5166756279636b672');"

In reply to Re: Re: Perl Advocacy: Sometimes java is bitter... by maverick
in thread Perl Advocacy: Sometimes java is bitter... by hackmare

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.


laziness, impatience, and hubris
	PerlMonks