>I don't use for-loops, because a while-loop can do the same, and it's too hard for me to learn. Pretty much. Older engineer. He remembers the transition from

>I don't use for-loops, because a while-loop can do the same, and it's too hard for me to learn. Pretty much. Older engineer. He remembers the transition from blackberry to Android and is not ready for another one. He almost advocates for the use of Vectors ... Unfortunately he is also Lead Engineer, which makes matters complicated. Kotlin is far from the only subject where we butt heads. I also had to put his nose on all the leaks created by his atrocious 'architecture' in order to start working on a fix. I don't think there is a good solution for that kind of problems other than throwing the towel and move to another company. I plan to emigrate anyway, so there is that. There are true reasons to avoid Kotlin at the moment though : -slower compilation (we have a huge codebase and dexing is already an issue). -the whole team needs to move to it and since we are more than a dozen, it is a significant task. -Kotlin does not support Android Lint, so common issues like using an API 21 method with minApiLvl = 17 can occur unnoticed.