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: 134

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

How Datadog Cut the Size of Its Agent Go Binaries by 77%

After the Datadog Agent grew from 428 MiB to 1.22 GiB over a period of 5 years, Datadog engineers set out to reduce its binary size. They discovered that most Go binary bloat comes from hidden dependencies, disabled linker optimizations, and subtle behaviors in the Go compiler and linker.

By Sergio De Simone

GitLab Suggests AI Can Detect Vulnerabilities But it's AI Governance that Determines Risk

Artificial intelligence is rapidly transforming how software vulnerabilities are detected, but questions about who governs the risks AI exposes, and how those risks are acted on, are becoming increasingly urgent, according to a new blog post by GitLab.

By Craig Risi

Cloudflare Releases Experimental Next.js Alternative Built With AI Assistance

Cloudflare released vinext, an experimental Next.js reimplementation built on Vite by one engineer, with AI guidance over one week, for $1,100. Early benchmarks show 4.4x faster builds, but Cloudflare cautions it's untested at scale. Missing static pre-rendering. HN reaction skeptical, noting Vite does the heavy lifting. Already running on CIO.gov despite experimental status.

By Steef-Jan Wiggers

Netflix Automates RDS PostgreSQL to Aurora PostgreSQL Migration Across 400 Production Clusters

Netflix engineers describe an internal automation platform that migrates nearly 400 RDS PostgreSQL clusters to Aurora, reducing downtime and operational risk. The platform coordinates replication, CDC handling, controlled cutover, and rollback, while supporting service teams in a self-service migration workflow.

By Leela Kumili

Presentation: 4 Patterns of AI Native Development

Patrick Debois discusses the evolution of software engineering in the age of AI. He shares four key patterns: transitioning from producer to manager, focusing on intent over implementation through spec-driven development, moving from delivery to discovery, and managing agentic knowledge. He explains how these shifts redefine seniority, team roles, and the future of the DevOps workflow.

By Patrick Debois

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service