My bud Matt Raible blogged about reading a Scala book and I mentioned Stuart Holloway's "Programming Clojure". Matt replied "I like Scala and Groovy and see no compelling reason to learn Clojure. Am I missing something?"

Good question. Eric Lavigne said a few things about Clojure that caught my attention:

"My knowledge of Groovy and Scala are very limited, but here are my impressions relative to Clojure.

Scala seems like a good programming language. Its static typing reduces its flexibility compared to Clojure, but may still be a good deal because it helps with catching errors more quickly. Scala also has been around longer than Clojure, and has used that time to develop more sophisticated libraries than are available for Clojure right now. So why is Clojure still worth learning? Scala gets much of its flexibility from having a lot of features built into the language. Clojure has a small number of language features that are carefully chosen to work well together. The result is a language that is both very flexible and very easy to learn.

One of the design goals of Groovy was to be compatible with Java code, but providing some extra features, just as C++ was designed to be compatible with C. This is a good thing if you have a lot of Java code that you want to migrate, or if you are uncomfortable with learning something new. However, Java is inflexible and overly complicated, and trying to maintain compatibility with Java prevented Groovy from being much better than Java. I quickly lost interest in Groovy so it's possible that I missed something - I would love to hear what advantages Groovy has compared to Scala or Clojure."

There's a Clojure group on the web and this spawned a discussion there entitled "Matt Raible: "Why is Clojure better than Scala or Groovy?"

Let's discuss this! There's a Clojure group... http://www.codetown.us/group/clojure Let's dip our feet in and see what all the talk is about. I'll start a discussion there. You can join in on the discussion: "Why Clojure?" in the Clojure group, where it belongs.


I am going to take another look at Eric's Clojure code that won the CodeTown Coding Contest #1 on Wari. It's a great way to see how things work from a practical perspective. The Compojure web framework is also something I want to see... Stay tuned!

Views: 280

Comment

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

Join Codetown

Comment by Michael Levin on January 19, 2010 at 11:32am
What are some examples where Clojure has fewer issues, Jackie?
Comment by Jackie Gleason on January 19, 2010 at 11:18am
I love Groovy but Clojure does seem to give you a lot of the simplicity with less byte code issues (although scala seems pretty good here). For now, however, I will continue using Groovy :-)

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

Presentation: The Human Scalability Problem: Why Your Teams Don’t Scale Like Your Code

Charlotte de Jong Schouwenburg discusses the "human bottlenecks" of hyper-growth. While systems scale, human cooperation often breaks down due to communication overload and lost context. She shares proven tools for behavioral scalability - including communication architecture and "engineering trust" - to help leaders maintain high-performing, autonomous teams without sacrificing speed or culture.

By Charlotte de Jong Schouwenburg

Article: From Batch to Micro-Batch Streaming: Lessons Learned the Hard Way in a Delta Index Pipeline

This article describes how a production delta-index pipeline migrated from scheduled batch to micro-batch Spark Structured Streaming. It covers why record-level streaming was rejected, how partition-based watermarks replaced fragile S3 completion markers, overlap-window correctness, and restart-as-design strategies for better predictability in object-store–based ingestion systems.

By Parveen Saini

Podcast: Roq: Leveraging Quarkus to Build Static Sites at the Speed of Go

Andy Damevin, a developer who worked on Quarkus for almost a decade, talks about Roq. A project that started as an experiment to try to see if it’s possible to build a static web site generator on top of quarkus. He touches on the rationale for choosing Java and Quarkus, how to migrate to Roq, and the platform's future.

By Andy Damevin

DoorDash Used Copilot to Convert Its XCTest-Based iOS Test Suite to Swift Testing

Using Copilot along with strong reliability safeguards, DoorDash migrated their iOS XCTest-based test suite to Swift Testing, thus modernizing a large test suite quickly, safely, and with measurable performance gains, says DoorDash engineer Matheus Gois.

By Sergio De Simone

Java News Roundup: OpenJDK JEPs, GlassFish, Spring AI, JReleaser, A2A Java SDK, Google ADK, Gradle

This week's Java roundup for April 27th, 2026, features news highlighting: OpenJDK JEPs for JDK 27; the fifth milestone release of Spring AI 2.0; the second milestone release of GlassFish 9.0; point releases of Quarkus, JReleaser, Gradle, LangChain4j and Google ADK for Java; the second beta release of Hardwood; and the first beta release of A2A Java SDK 1.0.

By Michael Redlich

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service