Some thoughts about Clojure, its latent potential and adoption

So I am at the point now where I can’t see myself really using another language for large stuff anymore. And luckily I don’t have to (for the foreseeable future).

Clojure is just that good. I gave up on selling it though, unless one genuinely asks me, and then I won’t stop talking :slight_smile:

I was a freelance programmer and I just introduced Clojure in multiple green field solo dev projects (some of which now grow and employ extra developers). The last of which is a now economically profitable bootstrapped SaaS company I founded, where I can spend my full time on. And if that grows more, I’ll be hiring Clojure devs too. So in a way that ‘marketing strategy for clojure’ worked out to some extent: there’s more clojure code bases than there were before :slight_smile:

Now: I am nowhere near the best engineer in the world, but I get the job done, and my code is generally well maintainable, so I am happy. (I made horrible things before my clojure time, on the maintainability spectrum, in Java, PHP, etc).

BTW: What I liked a lot is how easy it was to onboard other Clojure developers into a Clojure code base. Getting to learn other people’s code bases is way way less complex in Clojure than in most typed languages where people define their own ‘DSL’s’ all the time by class hierarchies and what not.

But how to REALLY market all that? No idea. No time either.

But it’s an absolute bliss when speaking to other people who also ‘get’ clojure. Because then there’s no need for convincing all the time.

So I leave with a shout out to @plexus: thanks for creating this forum! :clap:

6 Likes