Re: Java is the machine that goes "Ping!"

[Anonymous Monk]

I don't get it, you say:

I'm not going to get into the argument of whether Perl is better than Java or vice versa

But your post is just an implication that Perl is better than Java for glue code. This implication isn't backed up by anything, at all. If I misinterpreted your intent, then what was the point of the post (was there one at all?), I don't get it.

Saying we write this, this, and this in Perl doesn't mean much to me. Please provide explanations of why Perl's so much better for the tasks and include the Perl code (and corresponding Java code) so we can analyze it ourselves.

Better yet, before posting any Java vs. Perl threads, ask yourself "would I post this to a Java forum" and think about it for a while. This is essential to achieving REAL ULTIMATE POWER!

[thewalledcity]

Well Java does not have some of the lower level access to the system that you can get by using perl. (Every try getting a listing of PIDS and open ports to kill a runaway server in Java?) I think this boils down to: "use the right tool for each job". Java is pretty good for doing the Web Application thing (aside from the complexity of EJBs), but I would not want to write system maintance programs in Java.

[Aristotle]

That might be a good point, except Perl is rather pretty good for the webapp arena too.. :)

Makeshifts last the longest.