Hacker News Reader

Comment by exabrial | Hacker News Reader

No, there really isn't a need for all of them. SLF4J solves 100% of the problems 95% of the time. The problem is Apache's "Not invented here" syndrom. Commons-logging, Log4j, developers need to just abandon their projects and work on SLF4J.

BTW "architecture astronautism" great term. I <3 Java, it has a culture of overengineering, in which I do not participate.

View on HN

slf4j is a facade. It does not do much alone.

logback / log4j2 are 2 implementations of the slf4j facade. log4j2 is a community driven project and it is maintained with Apache License 2.0. It addresses some issues of logback. If you run into this issues in production, you can switch to log4j2, given that you are using slf4j (which is the recommendation).

commons-logging is pretty dead, and nobody makes a deal about it. It has not been updated for around 5 yrs.

You clearly need to understand the difference between slf4j and logback/log4j2. And you should learn more about what the Apache Software Foundation is doing. I consider it better not to trust a single company when it comes to important things. It has often proven in the past.

Whilst I am not a fan of the logging pain in java, not invented here would apply to anyone thats not log4j since they were really the first to get properly started.

Nobody cares who was first. The right thing to do would have been to focus on getting j.u.l right and then be a grown-up about it and ditch log4j.

Apache fucked up and Sun fucked up. And we all lose.

The creator of slf4j and logback originally created log4j, so "Not Invented Here" is literally not true as the inventor invented those three libraries.

Reply on news.ycombinator.com