Hello friends,
I'm launching an open-source project that I worked on during KotlinConf!
I've written a larger article or why I did this. Basically I got interested in Gradle+Kotlin because was fed up with the black magic in Gradle+Groovy, of not understanding neither how it works or why it doesn't work.
Rewriting your entire build to Kotlin can be daunting, but you don't need to do that. I have found out that adding just a bit of Kotlin to your existing build can relieve a lot of that Gradle frustration. And my project
@cedric I didn't use Kobalt per se, but it was instrumental for me to realize that things were not right with Gradle/Groovy.
In some sense Gradle moving to Kotlin proves you were right
j
janvladimirmostert
10/11/2018, 6:17 AM
the only reason i tried Gradle was due to the Kotlin script, Groovy was horrible. With the KotlinScript in place, i might just ditch Maven for Gradle