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.
perl -l -e "eval pack('h*','072796e6470272f2c5f2c5166756279636b672');"