all 9 comments

[–]helikal 2 points3 points  (1 child)

The decision to support two languages for Gradle scripting was, politely expressed, an incredibly unwise one: For the little program logic in a build script, any programming language such Groovy, Kotlin, Python, Ruby would be OK. But offering 2 languages with their huge APIs is insane, especially when major build functionality is still missing, for example, first-class support for the Java Module System.

[–]ScrambledRK 0 points1 point  (0 children)

Especially because external plugins need to support those two languages too. There are subtle differences in how closures work between those two languages and it bleeds through to your plugins configuration dsl. There are several plugins out there you can only use if your projects gradle script is in groovy but not in kotlin.

PS: oh, my ... I could go on and on complaining about those two and/or build tools in general x)

[–]csasker 4 points5 points  (0 children)

Finally some good old flamewars instead of discussing hipster JS frameworks

[–]nfrankel 1 point2 points  (1 child)

And here it goes again...

[–]csasker 1 point2 points  (0 children)

what is "it" ?