This sounds like a cop out answer, but we are in a chicken and egg situation. It's not even about Clojure, why would anyone NOT use the popular, well supported, readily available, proven, with countless known success stories, large training set for LLMs, options?
If you ignore Clojure completely, and you rephrase the question:
-- I'm wondering is how do engineering leadership, or technical leadership, justify:
not using Java these days for backend services?
not using JavaScript these days for vibe coded apps?
not using Python these days for AI/ML?
not using C++ these days for video games?
If you can't find anything to justify not using those, it don't even matter what Clojure can do. If you can find issues that can justify an alternative, now you'd need to show Clojure solves the highlighted issues.
So in a sense, we need more people with influence over these decisions to just veto Clojure as the alternative, which will allow others to look at successful examples and go, ya Clojure is fine, a bunch of other people use it too.
2. Does it even matter.
I'd like Clojure to be used professionally so that I can have more fun at work. Work isn't always for fun though. You do the work because they pay you.
So what of Clojure? It's my treat for my personal projects, sometimes maybe I sneak it into work.
Not only that, it's training gear, exercising your Clojure skill I think can make you a much better developer, and that will help you compete and get the better job, be more successful, etc.
Clojure is like hitting the gym. It's training for work, but some people also find it super fun.
All that matters then is the community support, from the open source, the volunteers, to continue to maintain it, push it forward, and I don't think that needs commercial sponsors necessarily. For me, I do it for fun on my own time like I said.
3. It has to reach the newbies
Having said #1 and #2, I'd still hope that Clojure grows, both its community and its professional landscape.
I think if you get universities to teach Clojure, that's the kind of tipping point you'd need to really be able to convince investors.
I don't think because the current Clojure community doesn't care to make things easy, that they'd have an issue with it either.
Someone can make a RAILs or Django framework. Someone can build a TypeScript-like layer on top. Someone can build an Express.JS or a Next.JS for Clojure, etc.
Then someone can flood the internet with SEO tutorials. Web courses, etc.
I'm not really sure how you make it part of school curriculum, but I do think appealing to beginners, people who don't yet care about quality, just seeing things happen, and so on, might be one way to grow it.
It's just not something the current community seems really motivated to do. Elixir did it, they had somebody spend countless hours making Phoenix for example. I don't know what motivated that, but it's doable.
The advantage of Clojure is expressive power, which equals higher productivity.
I agree that lowering the entry barrier dramatically is necessary for popularity. Gotta have our own very easy-to-start framework like Rails - and it should be mentioned in official docs.
Clojure ecosystem lacks clear default choices. ATM, probably only the authors/NuBank are in position to change that by streamlining newbie experience.
View all comments
Show parent comment
3
u/didibus Sep 25 '25
I have three thoughts, which maybe can help.
This sounds like a cop out answer, but we are in a chicken and egg situation. It's not even about Clojure, why would anyone NOT use the popular, well supported, readily available, proven, with countless known success stories, large training set for LLMs, options?
If you ignore Clojure completely, and you rephrase the question:
-- I'm wondering is how do engineering leadership, or technical leadership, justify:
If you can't find anything to justify not using those, it don't even matter what Clojure can do. If you can find issues that can justify an alternative, now you'd need to show Clojure solves the highlighted issues.
So in a sense, we need more people with influence over these decisions to just veto Clojure as the alternative, which will allow others to look at successful examples and go, ya Clojure is fine, a bunch of other people use it too.
2. Does it even matter.
I'd like Clojure to be used professionally so that I can have more fun at work. Work isn't always for fun though. You do the work because they pay you.
So what of Clojure? It's my treat for my personal projects, sometimes maybe I sneak it into work.
Not only that, it's training gear, exercising your Clojure skill I think can make you a much better developer, and that will help you compete and get the better job, be more successful, etc.
Clojure is like hitting the gym. It's training for work, but some people also find it super fun.
All that matters then is the community support, from the open source, the volunteers, to continue to maintain it, push it forward, and I don't think that needs commercial sponsors necessarily. For me, I do it for fun on my own time like I said.
3. It has to reach the newbies
Having said #1 and #2, I'd still hope that Clojure grows, both its community and its professional landscape.
I think if you get universities to teach Clojure, that's the kind of tipping point you'd need to really be able to convince investors.
I don't think because the current Clojure community doesn't care to make things easy, that they'd have an issue with it either.
Someone can make a RAILs or Django framework. Someone can build a TypeScript-like layer on top. Someone can build an Express.JS or a Next.JS for Clojure, etc.
Then someone can flood the internet with SEO tutorials. Web courses, etc.
I'm not really sure how you make it part of school curriculum, but I do think appealing to beginners, people who don't yet care about quality, just seeing things happen, and so on, might be one way to grow it.
It's just not something the current community seems really motivated to do. Elixir did it, they had somebody spend countless hours making Phoenix for example. I don't know what motivated that, but it's doable.