days
-6
-9
hours
0
-8
minutes
-5
-2
seconds
-3
-9
search
No longer groovin'

Pivotal cuts funding for open-source JVM language Groovy

Natali Vlatko
Empty pockets image via Shutterstock

Pivotal have announced they are withdrawing their support of Groovy and the accompanying Grails framework after their next major releases in March.

Yesterday it was reported that the company will fund the next two major releases of Groovy and Grails through March 31st 2015, after which it will no longer directly fund development on the popular open source projects.

The software company, based in California, explained it’s decision over on the Pivotal blog:

The decision to conclude its sponsorship of Groovy and Grails is part of Pivotal’s larger strategy to concentrate resources on accelerating both commercial and open source projects that support its growing traction in Platform-as-a-Service, Data, and Agile development.

While Pivotal have withdrawn their support, they are hopeful that other interested companies in the open source arena will take the reigns and lead the JVM language and supporting framework in a direction which can “best serve the goals of those projects.”

Seeking new sponsorship

The timeframe given by Pivotal aims to allow the new version releases, as well as the chance to acquire new sponsorship. Groovy’s founder Guillaume Laforge also reported the news via blog, citing the Groovy community as a key driver for the language, urging users to “help us find a solution to make Groovy shine as bright as ever.”

For Grails the story is much the same, with head developer Graeme Rocher updating his followers on his aspirations for Grails after the Pivotal funding deadline:

There is so much potential to unlock with Grails 3.0 in terms of building out support for new profiles targeting Netty, Hadoop and Asynchronous programming models. Regardless, of what happens in terms of sponsorship, both the Groovy and the Grails communities will continue to innovate and move forward as Open Source projects.

Pivotal’s decision to dump Groovy and Grails has been met with mixed reactions from the community, with many users on Reddit reacting surprised and disappointed: “Wow, didn’t expect that. I can see dropping Grails because of the (sadly) perpetually small usage of the framework, but Groovy is still finding use in tools like Gradle. It probably doesn’t align well enough with Pivotal’s cloud strategy.”

Author
Natali Vlatko
An Australian who calls Berlin home, via a two year love affair with Singapore. Natali was an Editorial Assistant for JAXenter.com (S&S Media Group).