Kotlin has indisputable benefits. It's terse, expressive, and addresses some of Java's oldest issues at the compiler level. For much of the code we write, the runtime performance difference is negligible.
Occasionally, however, a hot code path will reveal the truth about primitive boxing, immutables, capturing lambdas, or delegates. Do we have to abandon Kotlin to write faster code?
In this session we'll discuss:
Collin is a software developer with Livefront