No they are not Java folk - they are ksh folk whose argument for Java is rather superficial in my opinion, though that doesn't automatically mean they are wrong, of course. But thanks for continuing with your analysis! At least it warns me that I have to find out how to code these Java features for the Java vs. Perl benchmark tests - what I forgot to ask is what about comparative development time for a typical routine in Java vs. Perl - such costs will also have to be taken into account by management.
As I understand it, Java uses its own virtual machine - isn't that going to be slower than perl's use of the real machine via C, for example when using IO services?