ah, when I was consulting and introduced Kotlin, h...
# announcements
a
ah, when I was consulting and introduced Kotlin, had to give a speech about what it meant and that staying static was a problem. if they wanted to work with us, they needed to play by the rules of moving forward quickly, and we would always help them. Even a client that we no longer worked for, we offered free Kotlin migrations every milestone. Can you create a branch of the old dependency, upgrade it, release that with a new version, then use it in the new code that already needs testing anyway?