How will kotlin 1.3 scripting affect kscript?

Just read the RC release notes and stumbled upon:

There is a new public artifact: kotlin-main-kts. It contains a script definition and a minimal maven artifacts resolver in a single jar. Its purpose is to simplify the creation and usage of the simple utility scripts that may depend on the external libraries. For example, you can now write the following script:

@file:Repository("https://jcenter.bintray.com")
@file:DependsOn("org.jetbrains.kotlinx:kotlinx-html-jvm:0.6.11")
​
import kotlinx.html.*
import kotlinx.html.stream.*
​
print(createHTML().html {
    body {
        h1 { +"Hello, World!" }
    }
})

Then run it with only kotlin-main-kts.jar in the classpath:

kotlinc -cp <path/to/kotlin-main-kts.jar> -script sample.main.kts

This looks a lot like what kscript currently does … will you adopt the 1.3 scripting? Will this make kscript obsolete? Is this taking kscript to the core? What are your thoughts?

[oshai]

I had the same question myself

[holgerbrandl]

@CaelumF @moisesvs Doesn’t the problem rather point towards gradle and the ide. It doesn’t seem to be a problem with kscript itself, but I may miss the point here.