why should I use your lib instead of anko?

# anko

[david.bilik]

why should I use your lib instead of anko?

[louiscad]

That's a great question I should answer in depth in the library docs @david.bilik !
It's smaller because no need to subclass the Views for View DSL usage.
It's smaller because it's split, so no unneeded dependencies. You only pick what you need.
It's smaller because the View DSL lambdas are all inline, versus non inline in Anko
It's way more easily extensible in regards to View DSL as no subclassing boilerplate needed.
It's more active than Anko, I work hard on this project to deliver extensions you are very likely to need in an Android project
View DSL IDE preview doesn't need any IDE plugin that can break after each new release of Android Studio
It's smaller overall, all the modules are in total about 2K methods, counting the inline methods that Proguard will remove on release builds (you enable proguard on release builds, right?)

[david.bilik]

Thanks 🙂 I am a heavy user of anko so it will be very difficult for me right now to re-orient myself to a different lib, but I will give it a try on some side project

[louiscad]

@david.bilik Given how small are splits (of Splitties), you can try to add it to a project that already uses Anko! In fact, that's what I did for a few projects where I used Anko first.