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

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: Local First – How To Build Software Which Still Works After the Acquihire

Alex Good discusses the fragility of modern cloud-dependent apps and shares a roadmap for "local-first" software. By leveraging a Git-like DAG structure and Automerge, he explains how to move from brittle client-server models to resilient systems where data lives on-device. He explores technical implementation, rich-text merging, and how this infrastructure simplifies engineering workflows.

By Alex Good

Article: Stateful Continuation for AI Agents: Why Transport Layers Now Matter

Agent workflows make transport a first-order concern. Multi-turn, tool-heavy loops amplify overhead that is negligible in single-turn LLM use. Stateful continuation cuts overhead dramatically. Caching context server-side can reduce client-sent data by 80%+ and improve execution time by 15–29% .

By Anirudh Mendiratta

Presentation: State of Play: AI Coding Assistants

Birgitta Böckeler discusses the rapid evolution of AI agents, moving beyond "vibe coding" to sophisticated context engineering. She explains how architectural constraints and "harness engineering" create the safety nets required for autonomous code generation. She shares vital insights for leaders on balancing speed with maintainability, security risks, and the cost of AI autonomy.

By Birgitta Böckeler

Inside Spotify’s 2025 Wrapped Archive: AI Narratives at Scale and the Privacy Trade‑Off

Spotify's engineering team developed the 2025 "Wrapped Archive," generating 1.4 billion personalized reports for 350 million users. This system identifies key listening days and crafts narratives using a language model. As companies increasingly provide narrative recaps, concerns about user privacy and data tracking persist, necessitating a balance between insights and privacy safeguards.

By Matt Foster

Presentation: When Every Bit Counts: How Valkey Rebuilt Its Hashtable for Modern Hardware

Madelyn Olson discusses the evolution of Valkey's data structures, moving away from "textbook" pointer-chasing HashMaps to more cache-aware designs. She explains the implementation of "Swedish" tables to maximize memory density. She shares insights on systems intuition, memory prefetching, and the rigorous testing needed for mission-critical caches.

By Madelyn Olson

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service