> I'm sorry, but that's just you being in denial Have fun rewriting history then. Google picked Gradle, JetBrains, Kotlin, that's just the way it is. If they h

> I'm sorry, but that's just you being in denial Have fun rewriting history then. Google picked Gradle, JetBrains, Kotlin, that's just the way it is. If they had been interested in Scala on Android in any way, they'd put a couple of people behind it when it came out, or at least encouraged some 20% projects. That never happened. And it's perfectly fine. Nobody cares about the TIOBE index. Scala faces plenty enough of challenges within its core ecosystem, nobody would gain anything from targeting the Android runtime and SDK on top of that. Exactly the same way Spring developers don't give a damn about Android. > Apparently not via investing in tooling, though? That's a pretty ignorant comment given the amount of work that was delivered since the creation of the Scala Center. > What do you mean? There's a big difference between having to convert all the common data structures between Scala and Java, or simply reusing them, like Kotlin does. Plus, Scala's idiomatic usage of Option is fundamentally incompatible with libraries taking and returning nulls everywhere. Google made Kotlin first-class without having to break the entire SDK. That's a pretty huge reason Scala never stood a chance.