Not quite what I meant. I meant the set of people for whom Kotlin would be a good fit is largely (but not totally, I'd guess) a subset of those who would gain from using Scala. Therefore for any developer auditing languages, Kotlin and Scala are likely to be peers (as they were for me) and in that case, Scala being more established (i.e. more resources, more employees, more stack overflow questions) means Kotlin would struggle.
I just re-read the 'comparison to Scala' page, and that seems to reinforce that, e.g.: "if you're happy with Scala, you don't need Kotlin".
Which is not to argue my point: you know your goals far better than I. But if anything, take it as a gentle criticism of your messaging.
I just re-read the 'comparison to Scala' page, and that seems to reinforce that, e.g.: "if you're happy with Scala, you don't need Kotlin".
Which is not to argue my point: you know your goals far better than I. But if anything, take it as a gentle criticism of your messaging.