Gradle does also support “Gradle Kotlin DSL” and even seems to say this is the future for Gradle. The statement that “but groovy is obviously better for DSL” ( @darksnake ) is at least debatable, given that the people behind Gradle seem to now prefer Kotlin, although this is stiall a work in progress.
However, all gradle documentation is for Gradle Groovy DSL, and the documentation for Gradle Kotlin DSL, currently assumes the reader already is familiar with Gradle Groovy DSL.
At this time, if you don;t already know Gradle, you must first learn Gradle Groovy DSL, and then you can transfer to Gradle Kotlin DSL. Groovy is only needed to get started, so this is very frustrating if you do not already know Gradle before learning Kotlin.
In the same manner most Kotlin documentation assumes you know Java. So if you hire team members and wish to train them in Kotlin, the must first learn Java even though they will not program in Java.
This is all a transition problem, and will go away with time, but is frustrating for people coming to Kotlin who have not recently been in the Java/Gradle world.
This opens a window for ‘kobalt’: people adopting Kotlin but not from the Java/Gradle world. Kobalt promises the use of kotlin rather than groovy right now, and no need to learn a language (groovy) just to be able to read the documentation of Gradle Kotlin script!.
So @jpliska, I will take your advise and try kobalt, and if it goes well introduce it to our project teams.