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!

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 wrk from a practical perspective. The Compojure web framework is also something I want to see... Stay tuned!

Views: 93

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

Inside Google’s System for Coordinated A/B Testing Across Its Global Service Fleet

Google has shared details of its fleet wide large scale A/B experimentation system designed to standardize experiment assignment, exposure logging, and configuration propagation across distributed services. The approach enables consistent measurement across products, reduces experiment conflicts, and improves reliability of data driven decision making at scale.

By Leela Kumili

Presentation: Choosing Your AI Copilot: Maximizing Developer Productivity

Sepehr Khosravi discusses the evolution of developer productivity tools. Evaluating the strengths of tools like Cursor and Claude Code, he explains actionable techniques for senior engineers - including context engineering, custom rules, and Model Context Protocol (MCP) integrations. He shares real-world benchmarks and strategic frameworks for balancing AI adoption with clean code quality.

By Sepehr Khosravi

Article: Two Misconfigurations That Caused Spark OOM Failures on Kubernetes

After migrating Spark pipelines to Azure Kubernetes Service, two infrastructure settings interacted destructively: spark.kubernetes.local.dirs.tmpfs=true backed shuffle spill with RAM instead of disk, and a hard podAffinity rule forced all executors onto one node. Together, they caused repeated OOM kills invisible to standard diagnostics.

By Pranav Bhasker

Node.js Moves to One Major Release Per Year, Starting with Node 27

Node.js will change its release schedule starting with version 27 in October 2026, moving from two major releases per year to one. All releases will become Long-Term Support (LTS), removing the distinction between odd and even versions. An Alpha channel for early testing will also be introduced. This decision addresses maintenance challenges and aims to align with user needs.

By Daniel Curtis

Presentation: The Human Toll of Incidents & Ways To Mitigate It

Kyle Lexmond explains how to handle the high-pressure environment of severe production outages. He discusses the critical distinction between mitigation and root-cause resolution, sharing personal experiences from harrowing incident rooms. He shares valuable operational strategies on overcoming cognitive overload, establishing blameless cultures, and optimizing systems for faster recovery.

By Kyle Lexmond

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service