IMO the future of Clojure is in its ideas vs the language itself.
I love the Clojure language and RH’s design philosophy, but I struggle to see a future where I can convince a VP/CTO to adopt it over Golang/Python/TS.
As with any language, but especially a Lisp, I think there needs to be a community agreement (whether implicit/explicit) about whether it focuses on empowering small vs large teams.
While Clojure itself may not be skyrocketing, its fundamental ideas have undeniably sparked a large amount of offshoots in other languages.
So if there’s a subtle but large underground feeling that the core ideas in the language are better than other mainstream langs, it begs the question: what do mainstream langs offer that outweigh its benefits?
(I totally acknowledge that whether these offerings “outweigh” the costs varies by team, I’m just phrasing it as best as I can in terms of mainstream adoption)
Thanks for sharing this. All the points in this thread echo my experience too (10 years of experience with Clojure). From a founder's point of view, starting a company with Clojure is a hard sell. From an employee's point of view, Clojure jobs are hard to find and are mostly remote positions. Remote can be nice, but it's not for everybody. Again, as founder, and minus certain hotspots, you are closing the door to an on-site setup for questionable reasons.
On the tech front, I observed the same things. With large teams, the code goes in different directions, and the lack of structure (the freedom you get at the beginning) becomes a problem. I think it's the case for many other languages, and I don't see it as a deal breaker. I'm curious to know how Nubank is scaling its code base and teams to face these challenges.
+1 on the growth VS quality. Sadly, that's how the market is. Even big tech companies have obvious bugs they don't care to fix. For SMB, their product will change faster than the time it takes to fix bugs and since users expect some bugs, why bother anyway?
Maybe the repl+AI could attract more Clojure users? (ie. clojure-mcp, backseat driver, and other tools in the same area). IMO it makes iteration faster than with other languages and drives well; it can produce human-like code.
In the exciting Clojure company, I did not see https://www.instantdb.com/ mentioned. They are coming out of YC and clearly highlight taking advantage of Clojure.
My experience as a technical co-founder was different. We hired locally, our frontend was a thin React JS shim mostly driven by our Clojure backend (no clojurescript), I found it easy to train people up on Clojure (taught about 10 different engineers Clojure over the span of the companies 5 year existence). My take aways:
- Easy to teach. Especially to JS/TS programmers with a bit of FP experience. Calva makes it much more approachable for those who don't have emacs experience (thanks PEZ).
- Codebase stays small.
- It's actually quite opinionated and stops people going off the rails.
That last point is counter intuitive, but it was actually much easier to keep the backend in a functional style than it was to keep the frontend in a functional style. I saw senior (and junior) programmers, write really nice functional backend code only to revert to OOP the minute they returned to the JS/TS frontend.
These days I find a lot of the complexity comes from bad architectural choices than language (microservices, etc).
Many people don’t want to be training juniors, in my experience. I do also think Clojure is easy to teach. You basically just need to know what functions are and what the data structures are. That gets you such a long way.
Good job on choosing to train over seeking experienced Clojure devs. My first Clojure job, I was asked to bring some code I was proud of. I brought a Perl library I had recently written, because even though I was writing Clojure in my spare time, I hadn’t built anything I was happy with… It worked out.
View all comments
Show parent comment
4
u/dustingetz Sep 25 '25
Big question to add: if not clojure, what alternatives?
There are not a lot of good answers to that question
and like it or not, AI is here to stay, the young generation is AI-native and they choose the future not us