Keep Calm & Groovy On!

For nearly 20 years, Object Partners has been providing high quality software services. Roughly 7 years ago, we saw the potential that Grails and Groovy could offer our clients. So we invested. Heavily. We have developed hundreds of Groovy and Grails based projects for our clients all over the world. We have financially supported user groups and conferences, developed training courses, and have been very involved in the overall Groovy & Grails ecosystem and community. We have placed these technologies in the forefront when it came to our clients and our business.

So, you can say Pivotal’s announcement on Monday was a bit of a surprise to us. But, we’re not one bit concerned nor should you be. The technology landscape is a constantly shifting environment with new tools and frameworks coming and going. We have been a part of this shift as we have leveraged technologies such as iOS and Android, Spring Boot and Ratpack, Play and Scala, AngularJS, big data, and cloud computing to successfully deliver projects for our clients. Grails and Groovy will continue to be part of our toolkit and part of our client solutions in the future.

Immediately after this announcement, we started getting questions like, “Do we need a migration plan away from Groovy/Grails?”. The answer to that is an immediate and resounding “No”.

Both Graeme and Guillaume, as project leads for Grails and Groovy, have written about this development and how it will impact the teams. We’d like to emphasize, as they did, that both projects existed well before the SpringSource acquisition which eventually led to Pivotal’s sponsorship. Object Partners shares their opinion that not only will Groovy and Grails continue to exist after Pivotal’s sponsorship ends, but it will continue to thrive.

The community is not going to abandon these tools; neither should you.

We’d like to thank SpringSource, VMWare, and Pivotal for their stewardship of these projects over the last few years. Their financial support has allowed us and many others to enjoy these wonderful tools. Now it’s time to move on. Someone else needs to pick up the mantle. While we don’t have anything specific to share today, Object Partners, like many other companies and foundations, is looking into what we can do to support the Groovy and Grails teams going forward.

About the Author

Object Partners profile.

One thought on “Keep Calm & Groovy On!

  1. Owen Rubel says:

    Why would ANYONE migrate from a robust project with a strong community, tons of libraries, plugins and companies already supporting it? Plus it is already in the enterprise.

    Pivotal is stepping away because they can’t afford to support it and they figure it is robust enough for the community to support it now. Which it can… but it is always good to have sponsorship to keep the speed of development moving forward at the pace it has been moving at.

    1. Ehren Seim says:

      Agreed Owen!

Leave a Reply to Ehren Seim Cancel reply

Your email address will not be published. Required fields are marked *

Related Blog Posts
ML for Translating Dysarthria Speech (Pre-Part 1)
What is Dysarthria? Per the Mayo Clinic, Dysarthria occurs when the muscles you use for speech are weak or you have difficulty controlling them. Dysarthria often causes slurred or slow speech that can be difficult […]
Develop Quality Code
As software continues to dominate every facet of our lives, developers are faced with an ever-increasing pressure to produce bug free code. The responsibility of clean quality software falls upon everyone that is involved in […]
Clean JSX structuring in React
A video guide on how to structure your JSX to make it easier to know when it’s appropriate to split out new components. This will help keep your React code smaller, cleaner, and more DRY.
Wrapping a GraphQL Service With a REST API
Use Case Background Providing a GraphQL service on top of REST APIs is a typical GraphQL use case (e.g., https://graphql.org/blog/rest-api-graphql-wrapper/). Doing so can dramatically improve efficiency and flexibility, allowing data consumers to request only the data […]