mikemybytes

I guess that's why Kotlin became so popular in the Android world - all the new & shiny features are present but you still can target older bytecode versions

Thanks for the feedback! (author's here)

I promise to be more careful when picking up the title next time. I hope that the article's content somehow compensated that ;)

Thanks for the feedback! (author's here)

Sorry to hear that it could be confusing. I will look at its contents once more soon looking for some improvements.

Thanks for the feedback! (author's here)

IMO the problem with calculating precise savings is there is no "standard" use-case that could be used as a reference. I took one real-life application as an example in order to be more precise than just "it's somewhat faster", but the benefits will differ based on many different things (platform, app size, frameworks, etc.).