This is a terrible report.
Some of it is just flat wrong (e.g. the perl error message only exists if you write it -- if the developer didn't check for errors, they just don't show up).
Much of it is just "I haven't learned to do my job."
Some of it is just flat wrong (e.g. the perl error message only exists if you write it -- if the developer didn't check for errors, they just don't show up).
Much of it is just "I haven't learned to do my job."
The point of the article is that java makes his job harder. There are standard tools (syslog, truss, ldd) that he uses to troubleshoot problems under unix, and java supports zero of them.
It's not hard to get java using syslog if you really want it to (I wrote a syslog client for java, but ended up deciding it wasn't right for my problem).
ldd typically doesn't make much sense in a java deployment, because people typically will publish all of the parts together in such a way that it's fairly obvious what pieces are in use.
If we're all attached to all of our tools, we can never make progress.
A bit of googling found this:
http://stefanparvu.blogspot.com/2007/08/java-for-sysadmins.h...