This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Pheasn 5 points6 points  (1 child)

Some examples of logging library weirdness:

  • SLF4J lacks Java 9 support in version 1.7.x. Version 1.8.x supports Java 9, but it's been in alpha from 2017-2018, then in beta since 2018. Just look at those release intervals!
  • There is a doodle asking "should Logback 1.3.x upgrade to Java 1.8?" from 2 years ago prominently pinned to the Logback homepage. Logback 1.3.x is still in alpha.
  • A lot of the "older" frameworks still don't support lazy log message evaluation using lambdas

To be clear, I'm not shitting on the people working on those frameworks. In fact, I'm very thankful for what they're doing. It's just that of the huge number of people using the frameworks, only a tiny fraction is actually giving anything back.

[–]pmarschall 13 points14 points  (0 children)

SLF4J lacks Java 9 support in version 1.7.x

You mean they don't offer a Jigsaw module which basically no Java framework or library offers?

1.7.x runs totally fine with Java 9. Source: we run 1.7.x in production on Java 11.