Re: System.out.println() vs Logging, was Re: JComboBox.setSelectedItem() doesn´t update selected Item?

RedGrittyBrick wrote:
Lew wrote:
Pathetic.

RedGrittyBrick wrote:
Cruel *** ;-)

Sorry. Intended only for rhetorical effect. All feelings hurt in this newsgroup are the sole responsibility of the reader, blah blah blah.

Logging takes all of five minutes to learn.

I spent hours trying to find out what logging classes were available, which were widely used and whether any were a standard part of JRE 1.5.

Actually, this is a common problem with Java, all right. I found that log4j was very simple, adapted well to learning a little at a time, and relieved me of all worries about re-instrumenting for production. I therefore ignored all the other choices.

You should actually learn to use, say, log4j, before you pass judgment. Try it, you'll like it.

I will try it, but I suspect I'll probably still use System.out.println() in small programs (one or two classes, < 200 LOC).

Or maybe you won't like it. It took me a few projects to even bother to set up a log4j.properties for a project. Its simplest uses did enough for a while, at least as much as println() and with much less footprint.

Doubtless a Java client *can* be just as concise and easy to learn but the above were almost straight from the first tutorials I found. I've not found a simple Java tutorial that only uses classes that are part of the standard JRE.

It's a fair cop. Java can be a real beast.

--
Lew
.