[agigao]

Only paradigm isn’t enough. Language design, ecosystem and pragmatism is essential as well and Clojure has all that.

After a couple of years of writing Java in my late teen, early 20s, I observed considerable overhead and inefficiency while working on large Java projects.

I thought we shouldn’t have to recompile the whole project upon every single change.

Classes and private public fields, methods felt like they were solving the wrong problem.

Other fancy words, that contained fairly simple ideas, felt like the output of clever language designers who enjoy the sound of their voice.

Those were the issues I observed as a newbie, but still I started looking for alternatives and found Clojure fairly soon. Sense of satisfaction steadily grew as I dug deep into the language, it was addressing so many design decisions I questioned before. At some point I started re-writing core library and it was joy to see how simple a programming language can be.

I wrote software in many different programming languages over the years but writing Clojure at work is fun, multiplied.