But these languages use this approach because they...

# scripting

[gildor]

But these languages use this approach because they pure scripting, it's just default behavior. With Kotlin (Gradle/maven/kobalt etc) you can use not only scripts, but binary dependencies too.

Again, I don't want to restrict anything, If you really think that pure scripting approach for project build is good, okay, I just think that it should not bee the part of Kotlin itself. We already have a few build systems that support Kotlin, and I just see no advantages of pure scripting approach.

But, there is another case: Kotlin supports now JVM and JS, and will support native in future.
And we definitely need some way to publish pure Kotlin dependencies, without compilation them too Jar/Js, if we want to use them in js and native projects.
And probably​ golang or some scripting language dependency manager approach can work for such case. But I still think that it can be achieved as Gradle plugin, then new build system as part of Kotlin