Hello everyone.

I'm considering to use Groovy as the primary language at the company I work. I'm thinking that Groovy is the perfect language for the company but I need to know how big is the community support of the Groovy project. I can't use a language that can be dead in 10 years and I don't know if this is the case of Groovy.

Could you help me with this?
1
Bill Turner's profile photoFernando Franzini's profile photoKent Damgaard's profile photoCanadian Tracks's profile photo
7 comments
 
Support is great. If you look at tiobe index, Groovy open source contributions and development is really active. 
 
Groovy community is very active even tough every year there is a genius claiming Groovy is dead... but it's still here after 13 years and since has moved to Apache it is downloaded a way much more than ever before. So be sure Groovy is going to stay for a while
 
If the support for the language you choose were to vanish within 10 years, what would happen to your company?
 
If you are a Java programmer you already are a Groovy programmer, you just don't know it yet.
 
Ten year is a long look into the future. If you take the long view, you also need to think about where the rest of your system will be in ten years, will you still have browser based clients? Will you have the same database or whatever store you use. Since Groovy is a JVM language, how will the JVM look in 10 years? If you are concerned with your investment into a legacy codebase, you might want to look into how people are currently dealing with Cobol code on IBM mainframes and similar things - often the old code is still around, but accessed through some kind of service layer. So if you make sure that you have well defined interfaces to your code, you stand a better chance.

Also, how maintainable will your code be in 10 years? I've just finished a major rewrite of a system made for Grails 1.3.5. The original code was not written with I8N in mind, and all the external systems it connected to were changing their interfaces. It was cheaper and more efficient to re-write based on the original spec than to try and refactor the old code.
 
Groovy is great. But I would never use it as a primary language because it is hard to debug and too type-flexible.

Groovy is great for scripting, quickies, templates, and more. But it falls down when used as a replacement for Java/C#/.Net/etc.

I love Groovy but would use it only as a supplementary tool.
Add a comment...