Logging always seem "easy" but then I remember reading https://google.github.io/flogger/anatomy.html Even the variadic approach of some logging implementations comes at a non-negative cost
On Tue, Mar 25, 2025 at 6:12 AM Federico Valeri <fedeval...@gmail.com> wrote: > > Hi Clayton, thanks for raising this point. I think it's easier to keep > slf4j because it is widely adopted. Anyway, regardless of the final > choice, the alternative deserves a mention in the rejected > alternatives with some motivation. > > > On Mon, Mar 24, 2025 at 9:42 PM Clayton Wohl <claytonw...@gmail.com> wrote: > > > > Thank you for the response, Chia-Ping Tsai. > > > > The sl4j and System.Logger APIs are very similar and lightweight. Is > > there any particular API or functionality missing from System.Logger? > > > > Yes, all logging libraries/providers support System.Logger. > > > > Libraries like log4j2, which is what Kafka defaults to, support > > System.Logger (also called jpl or Java Platform Logging) directly, so > > you do not need SLF4J at all, and can remove a third party dependency > > from the project. > > > > Libraries like logback do not support System.Logger directly, but you > > can use the bridge org.slf4j:slf4j-jdk-platform-logging to route log > > messages from System.Logger to SLF4J.
