Programmer and mathematician. Problem solver. Lover of clean code, coffee, cycling, running and Italian food.
Kotlin, Java, Spock (Groovy), PHP, Angular, MariaDB, ...
(Background: In my team we have an active debate going on for the last months about switching to Kotlin. We have been using Groovy for some years but feel that the language is slowly 'dying' and getting less interest in favour of Kotlin.)
Groovy has been evolving for years and Groovy 3.0.0 will be released with lots of new features this year, so Groovy is not 'dying' and will not be die.
Thank you for the great work you're doing to groovy 3.0, I still believe that groovy should become one day fully static compile in order to live longer, maybe it's in the roadmap of 4.0, and it's ok to deprecate things that prevent that from happening.
I think they're both very interesting languages, and of course, once a new language comes along its "competitors" start losing some track in the community.
In the end I believe they will coexist, but be narrowed down to their specific purposes/applications. They both have their own strengths.
What are you guys using Groovy for? In your place I would start new projects in Kotlin, just to see how it goes, but not migrate old ones.
Programmer and mathematician. Problem solver. Lover of clean code, coffee, cycling, running and Italian food.
Kotlin, Java, Spock (Groovy), PHP, Angular, MariaDB, ...
What is your view on Kotlin compared to Groovy?
(Background: In my team we have an active debate going on for the last months about switching to Kotlin. We have been using Groovy for some years but feel that the language is slowly 'dying' and getting less interest in favour of Kotlin.)
Groovy has been evolving for years and Groovy 3.0.0 will be released with lots of new features this year, so Groovy is not 'dying' and will not be die.
Thank you for the great work you're doing to groovy 3.0, I still believe that groovy should become one day fully static compile in order to live longer, maybe it's in the roadmap of 4.0, and it's ok to deprecate things that prevent that from happening.
Hey Hidde,
I think they're both very interesting languages, and of course, once a new language comes along its "competitors" start losing some track in the community.
In the end I believe they will coexist, but be narrowed down to their specific purposes/applications. They both have their own strengths.
What are you guys using Groovy for? In your place I would start new projects in Kotlin, just to see how it goes, but not migrate old ones.
Yes, we have no trouble using Groovy for multiple projects. It is a great language.
Whad I personally miss the most in Groovy (versus Kotlin) is the type safety of all kinds of closures. And nullability.
For the more scripting side of things, Groovy might remain a better option than Kotlin in some cases.