Hello fellow Kotliners! I have started writing a ...

# kotlin-logging

[Michael Strasser]

Hello fellow Kotliners!

I have started writing a new, pure-Kotlin logging library. I am doing this to scratch an itch about the limitations of the Java libraries we mostly use.

I want a logging library that:
• is pure Kotlin (eventually multi-platform) and uses Kotlin idioms
• feels familiar for experienced developers to use
• natively uses structured logging and supports message templates to make that easy
• uses coroutine scopes, where contextual information can be put to be included in structured logs
• has microsecond or better timestamp resolution.
I want to call it Klogging because that is easy to say and remember. I have found Maxim Shafirov’s https://github.com/shafirov/klogging but it appears to be languishing in disuse. It also uses SLF4J under the hood for the JVM.

Maxim has indicated that he is happy if I reuse the name Klogging and suggested I ask around here.

What do you think if I reuse the name?

[George Ginzburg]

Hey!
I'm also interested in native logging for Kotlin and I would like to contribute. Could you write tickets in GH issues or introduce a roadmap so I could pick something to work on?
Thanks!

[Michael Strasser]

Thanks @George Ginzburg I will get moving on that soon. I have opened Discussions on the GitHub repo so please add suggestions there.

[George Ginzburg]

Hey @Michael Strasser
I've played around with the project and I'm ready to code something, but if I understand correctly, you are planning on reworking the existing api, project structure etc.
So, is it ok if I do part of the work (e.g. refactor some methods to interfaces) or I better hold off with code changes until you've done some initial cleaning up so we don't end up doing the same thing?

[Michael Strasser]

Hey @George Ginzburg, please hold off until I have set out a roadmap. I have been working on publishing what I have so far to Maven Central, which is taking some time.
Also, I am working on Klogging outside my work hours.