Discussion on "Pretty Logger for Java - improve the aesthetics of java console apps"

madalin ilie · 2020-12-16T13:03:08.576Z

Overview Java might not be the first choice when wanting to build command line applications, but as a Java developer myself, I don't see any reason for not doing so. With the rise of frameworks like Spring Boot or Quarkus and GraalVM you can create f...

Being new to java, this is mind blowing to me! I can't wait to dig into this. Just so I am clear, I would need to be using slf4j to use pl4j?

pl4j is a wrapper over sl4j. So by using pl4j you will actually interact with the sl4j api. This is implicit and nothing else is needed. But what you need is an actual implementation of sl4j, presumably logback. There is an example in the project with a TestClass and a logback.xml configuration file.

madalin ilie Got it! I'll check this out. I've never been so excited to log things to the console!

IMHO, this is not the right abstraction level to handle it.

SLF4J is an API. The "prettiness" is an implementation detail and should be handled by the underlying logging engine. You could move to the Appender level - and yes, it would require one such appender for each implementation (Logback, Log4J, etc.).

It's true. It might not be the best abstraction, but I like the benefit of explicitivness i.e. the ability to call methods that will mark the logs accordingly. I prefer to say complete rather than info with additional configuration. Sl4j (and implementations) supports a limited number of log levels. Using this library, even if the log levels remain the same, you can explicitly call the intended marker method. And it's still decoupled and require no change in the logging patterns.

Discussion

Pretty Logger for Java - improve the aesthetics of java console apps

Responses(2)

Recent in Forum

Search Hashnode

Pretty Logger for Java - improve the aesthetics of java console apps

Responses(2)

Recent in Forum