:speech_balloon: Hello everyone! After some intern...
# anko
y
💬 Hello everyone! After some internal discussion, we decided to deprecate Anko. Some of you already knew about it, and now it’s official. You can find the details here: https://github.com/Kotlin/anko/blob/master/GOODBYE.md. Thank you for your continuous support throughout these years!
😔 5
👋 6
😭 5
👏 1
l
Hello! Thanks for the update. Anko has been a good inspiration for me while I was getting started in Kotlin, and later when I worked on #splitties, so thank you for the effort, that definitely helped move the Kotlin ecosystem forward, and I'm pretty sure you inspired AndroidX KTX too. Now, I'm wondering what you've been and are working on at JetBrains! 🤔
h
@yan I’m really sorry that Anko has to go, but I also understand why. I use
AnkoLogger
as my default Logger, is there something that you recommend in substitution like Timber? @louiscad I don’t see nothing in splitties. Is there something that I didn’t see? Any plans to add it? Finally I will just use this spot to thank you to both of you for your work and contribution to the Kotlin community 💯🥇❤️
l
@hugo.matilla I personally use
Timber
. Splitties is now headed multiplatform, so if I was to add a logger, I'd want to make a multiplatform API (making the task a little tougher). It's not my focus right now and it requires some time to think about how to do it right, so ideas and use cases are welcome. Feel free to open an issue in Splitties project or start a discussion in #splitties channel.
h
I will think about it and if I came with a nice idea i will tell you. Thanks for the answer.
y
@hugo.matilla, you know, Anko is under Apache 2.0, it’s not that hard to move AnkoLogger out :)
3
h
Sure, I will do. thanks 😉
t
My first OS contribution. 😢
l
OS contribution? Edit: You probably meant OSS.
t
Yes, that.
c
#compose