Codetown ::: a software developer's community
Slightly modified from original post: http://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 ratpack, grooscript, 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.
Update: Groovy Moving to a Foundation
Comment
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
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.
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.
Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.
Check out the Codetown Jobs group.

Mallika Rao discusses the hidden risk of evaluation debt in production AI systems, drawing on her experience at Twitter, Walmart, and Netflix. She explains why traditional metrics fail modern architectures, breaks down a five-layer evaluation stack spanning infrastructure and UX, and shares a diagnostic maturity model to help engineering leaders eliminate silent semantic failures.
By Mallika Rao
The Cloud Native Computing Foundation has highlighted a new AI-assisted migration approach that enabled engineers to migrate 60 ingress-nginx resources to Higress in roughly 30 minutes, demonstrating how artificial intelligence is increasingly being applied to modernize Kubernetes networking and gateway infrastructure.
By Craig Risi
GitHub reports cutting token costs in agentic CI workflows by up to 62% by pruning unused MCP tools, swapping some MCP calls for gh CLI, and running daily “auditor” and “optimizer” agents. A token-usage.jsonl artefact and an Effective Tokens metric help track spend across models and spot regressions.
By Mark Silvester
Trisha Ballakur discusses her journey from a backend software engineer to CTO and CEO, using her startup Pointz as a case study. She explains how to implement bottom-up customer discovery to find product-market fit, effectively delegate to global contractors to reduce build times, customize open-source repos like Valhalla, and apply engineering test-case models to business development.
By Trisha Ballakur
AI bias mirrors human bias; both stem from our language and lived experiences. Ethics and AI are inseparable, but AI changes affordances, making harmful actions easier to carry out. The EU regulations apply to AI, since digital products are products. The ultimate goal is accountability: companies must ensure transparency, and laws should favor using the simplest AI that gets the job done.
By Ben Linders
© 2026 Created by Michael Levin.
Powered by
You need to be a member of Codetown to add comments!
Join Codetown