Clear questions and runnable code
get the best and fastest answer
Java is the machine that goes "Ping!"by Steve_p (Priest)
|on Dec 31, 2002 at 04:05 UTC
While watching The Meaning of Life last night, I realized that, at least where I have worked, Java is the machine that goes "Ping!" Now, I'm not going to get into the argument of whether Perl is better than Java or vice versa. It's just that when management needs an update on the development work in our area, Java is all that is talked about. While we are doing some good work with Java, a very important part of the system is left out. Perl is essentially the glue that holds the system together.
For our day to day work, and scripts to actually run the system, we use Perl. Perl works much better for our purposes than any shell script to start the system up. When developing, we use Perl for our check-in/check-out scripts with RCS. Our system monitoring programs are all written in Perl. Nearly all our support tools for reporting and manipulating data within the system are written in Perl. With all this, Perl remains the ugly step-sister in our environment.
Now, this is not the first time I've run across this problem. In the environments I've worked in Java is often in the fore front, while all the work that Perl does is hidden, even from the developers' direct managers. Is this a common occurance for all of you that work in a Java/Perl environment?