Re:Kotlin 1.1: What’s coming in the standard library
by mike_hearn on Wednesday January 25, 2017 @04:03AM
(#13479882)
Kotlin's design was heavily influenced by Groovy. You can see it in the builder DSLs, the syntax, the fact that Gradle is adding support for Kotlin alongside Gradle, and comments by the Kotlin designers. The big difference of course is that Gradle is dynamically typed by default.
Re:Kotlin 1.1: What’s coming in the standard library
by vorg on Wednesday January 25, 2017 @05:37AM
(#13480291)
> Gradle is adding support for Kotlin alongside Gradle, and comments by the Kotlin designers. The big difference of course is that Gradle is dynamically typed by default.
You've fallen for the trap of mistaking Gradle to be Apache Groovy, perhaps because those 10-line build scripts for Gradle are the only encounter most programmers have with Groovy. Your comment should read "Gradle is adding support for Kotlin alongside Groovy, and comments by the Kotlin designers. The big difference of course is that Groovy is dynamically typed by default."
Re:Kotlin 1.1: What’s coming in the standard library
by mike_hearn on Wednesday January 25, 2017 @07:58AM
(#13481013)
You're right - I know the difference but apparently something got corrupted between brain and keyboard!
Re:Kotlin 1.1: What’s coming in the standard library
by relics443 on Wednesday January 25, 2017 @06:49AM
(#13480631)
It's similar to Groovy, which I've worked with non extensively, but I think it adds a lot more. I've always found development in Groovy to be closer to Ruby or Python, while Kotlin feels more like Java (just better :-)
Are there any benefits or tradeoffs, based on what you might know about Groovy?