It’s unclear which “that” you mean here, but: - if you’re alluding to the idea that Kotlin would be driven in the direction of closed source compilers and tool

It’s unclear which “that” you mean here, but: - if you’re alluding to the idea that Kotlin would be driven in the direction of closed source compilers and tooling in order to “milk” enterprise adopters: that would require a bizaare set of changes, including changing the license of both the tooling and the compiler - neither of which require copyright assignment, so JetBrains are not even free to do. - if you’re betting on an open compiler but closed tooling, again that would require changing the license of the tooling, which JetBrains is not entirely free to do since it does not get assigned copyright on contributions. I don’t know what agreement JetBrains has in place with Google, but I’d wager it precludes making Kotlin proprietary.