java logging confuses the crap out of me so many libs and ap

Question

java logging confuses the crap out of me so many libs and apis it s a bit of a mess

elect · Answer

you mean it s fun trollface

bmsantos · Answer

Wait until u get into JS world

bmsantos · Answer

I always default to slf4j and log4j2 async logging

codeslubber · Answer

it s a dumpster fire and a laughable case in point of how poorly choices were offered logging other logging then logging compatibility

bmsantos · Answer

Common guys it isn t that bad considering the years that Java already has on its shoulders

codeslubber · Answer

assume you are joking Bruno I have been using KotlinLogging lately I like that thing

sreich · Answer

yeah kotlin logging seems nice thus far

bmsantos · Answer

Not joking But haven t used Kotlin logging yet I m sure it is an improvement over other frameworks In time things end up being replaced with something better hopefully

bmsantos · Answer

Apparently Kotlin logging is built on the top of slf4j

bmsantos · Answer

Because it is a wrapper around slf4j I m assuming that if you use Kotlin logging one still needs to add a specific slf4j bridge like log4j log4j2 Java logging logback etc

bmsantos · Answer

Or do they provide their own

codeslubber · Answer

no you are right

codeslubber · Answer

and that was a hassle I thought astounding to me that there were not simple docs for adding it to a gradle based build

codeslubber · Answer

but once I got it working I do like the kotlin sugary ness of being able to use $s and the fact that there is no work to only output if log enabled what logback brought

sreich · Answer

Yeah agreed I had to do this just now went with log4j

codeslubber · Answer

I still find logging immensely useful

codeslubber · Answer

running unit tests all the time over and over

codeslubber · Answer

if I don t know why something failed

codeslubber · Answer

I add a log message and rerun

codeslubber · Answer

for the pain of logging in J K at least we have good loggers when writing Swift you are still stuck with NSLog which is a complete joke

codeslubber · Answer

not really any better than a print statement

bmsantos · Answer

< sreich> if you intend to use threading or use an async toolkit framework make sure you use log4j2 or any other logger that supports async logging otherwise you might block your threads I default to log4j2 because of this

sreich · Answer

oh shit

sreich · Answer

< bmsantos> i use compile org slf4j slf4j log4j12 1 7 25

bmsantos · Answer

bmsantos · Answer

And simple async conf <https github com bmsantos vertx graphql example blob master graphql service src main resources log4j2 xml>

bmsantos · Answer

< sreich> nice game Love Terraria Will have to give it a try

sreich · Answer

thanks slightly smiling face don t expect gameplay right now it s just a tech demo state atm

sreich · Answer

thanks for the logging stuff good thing you mentioned something i was going with slf4j and log4j1 2 got it working withh your example now