Slightly modified from original posthttp://adamldavis.com/

There’s a hot new programming language that I’m excited about. It can be used dynamically or statically-typed, your choice. It supports functional programming constructs, including first-class functions, currying, and more. It has multiple-inheritance, type inference, and meta-programming. It also integrates really well with a battle-tested enterprise-worthy language and best-of-class virtual machine.

This programming language actually isn’t that new. It’s from 2004, but they’ve recently added a lot of new features, such as traits. Oh, did I mention it has a great community and tons of frameworks built on top of it for web-applications, testing, and even full build systems. This language is great for building DSL’s and is very light-weight. Oh, and it can be compiled to JavaScript and it can be used to develop for Android.

As you might have guessed, this language is called “Groovy”. The virtual machine it’s built on is the JVM, the web framework is Grails, the testing framework is spock, and the build system is Gradle.

As you may have heard, Pivotal has dropped its Groovy/Grails support. Although some will take this news as sky-falling bad news, I actually think it’s the opposite. Pivotal only "acquired" the developers behind Groovy and Grails through a “Russian nesting doll” turn of events. In short, SpringSource bought G2One then Pivotal bought SpringSource (and VMWare goes in there somewhere).

There are tons of companies that stand to benefit from Groovy that could take up its funding: Google, Oracle, and Gradleware come to mind.

Groovy has a lot going for it. With projects like ratpackgrooscript, gradle, and others, its future looks bright.

Also: Grails has improved dramatically and will support microservices much better in the next release (3) among other improvements.

UpdateGroovy Moving to a Foundation

Views: 158

Comment

You need to be a member of Codetown to add comments!

Join Codetown

Comment by Jackie Gleason on April 24, 2015 at 9:27am
In my world people aren't letting the news worry them too much. No plans to switch back to spring but I do think this highlights one of the weaknesses of Groovy. It is a lot harder to convert a Groovy file into a Java file than the reverse.
Comment by Adam Davis on March 5, 2015 at 4:47pm

Update: Groovy stewardship is moving to the Apache Software Foundation.

Here's a great article by Cédric Champeau (one of the developers behind Groovy) on Groovy's history and who has contributed to it over the years: http://melix.github.io/blog/2015/02/who-is-groovy.html

Comment by Adam Davis on March 1, 2015 at 9:56am

Clarification: Groovy and Grails are open-source projects. I used the short-hand "acquired" to describe Pivotal's hiring of the developers behind Groovy and Grails. Groovy and Grails development would continue even if no one hires these developers, just at a slower pace. 

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

Beyond Autonomous Teams in Software Product Development

Autonomous teams are an article of faith in modern software development. The shape of our value determines what we can do; it determines our trade-offs between agency and coherence. We all have a purpose, and we all have agency to do something, hence the suggestion is moving from product focus to value center thinking.

By Ben Linders

Presentation: Accelerating Performance by Incrementally Integrating Rust Into Existing Codebase

Lily Mara explains how to avoid high-risk software rewrites through incremental FFI refactoring. She shares how engineering teams can replace Python bottlenecks with Rust via PyO3, demonstrating how to achieve dramatic function-level speedups, seamless integration testing, and meaningful infrastructure cost savings without microservice overhead.

By Lily Mara

Article: When Spec-Driven Development Pays Off

AI coding assistants have become a core part of software development. AI-generated code has shown productivity gains, but it's also contributing to security weaknesses and familiar bug patterns. In this article, author Nitin Garg highlights the bottleneck has moved from code generation to code verification, and how to detect & mitigate it when the AI-generated behavior diverges from the intent.

By Nitin Garg

IETF Publishes RFC 10008, Adding the QUERY Method for Safe Requests With a Body

In June 2026, the IETF published RFC 10008, introducing the QUERY method to HTTP, the first new standard HTTP verb since 2010. QUERY enables developers to send richer query filters in the request body while maintaining cacheable, safe, and idempotent semantics. This addition addresses long-standing limitations with GET and POST methods, facilitating improved API interactions.

By Daniel Curtis

CPython Officially Adds RISC-V Support As a Tier 3 Platform

The Python core development team has officially recognized RISC-V as a Tier 3 platform in CPython, following extensive community collaboration on its implementation. Ongoing efforts aim to enhance integration into the continuous testing pipeline and move towards Tier 2 support. Feedback from developers with RISC-V hardware is encouraged to improve stability and performance.

By Olimpiu Pop

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service