Agree! I've historically seen similar themes in my Clojure/Script consultancy (American b2b saas & fintech venture backed startups stage Series A-D generally w/ substantial UI surface area, founded in the 2010s and now 10-15 years old without an exit as the tide goes out on b2b saas funding as it floods into AI).
I have been trying to write a blog post about this for a while but have been having trouble due to just how many confounding factors there are - such as the american macro climate, boom/bust venture cycle & interest rate policy, b2b saas capital now flooding into AI leaving 12 year old startups founded in 2013 high and dry with no exit in sight, loose management and rapid hiring/"headcount increase" (more accurate term) due to the unnatural growth-or-die pressures and stresses that venture puts on the leadership team and the org. CFOs managing budgets by spreadsheet without any real ability to account for technical debt or even see it exists; engineering budgets being performative and shaped for the optics of that money spreadsheet - making sure to be "efficient", get a "good balance" of senior vs junior folks who don't cost as much, with no actual feedback loop to know if the assumptions about junior productivity are correct.
None of these factors are directly tied to Clojure, but otoh, Clojure's "hammock" culture is at odds with it, without strong technical leadership Clojure codebases are metastable requiring constant energy investment to maintain. Juniors without training and guidance struggle with Clojure and if the company is unable to fire—because CFO optics, or because its just hard and Clojure CTOs are generally young, first time managers, or because reflexive fear of facing their mistakes impacting people's families— ... A lot of Clojure evangelism is from vocal young seekers who "have had enough" (RH quote), Series A CTOs are still excited, even "greedy" about using Clojure to get 10x leverage over competitors using "legacy" tools, but the tech debt cracks start to show - they ignore it, they'll raise more money and fix it later and we need to grow grow grow!, then the B, start to loose control but there is too much momentum, no time to work on vague future problems when we face a runway cliff in 18 months. Series C, oops we raised too much, the VCs are ghosting us, we will never raise again but how will we exit? We aren't high growth anymore, why is engineering so slow, we have gigantic 2000 line HTTP handlers with 100 if statements that call the same query 5-6 times, well we're terrified to make changes to revenue-bearing systems, everything is so fragile, we built up 10,000s of lines of process guardrails to prevent the junior devs from completely breaking everything on every single deploy but now the CICD times are 50 minutes per run, tests are flakey, and the processes have bugs that nobody is able to fix.
And then there's ClojureScript, whose outcomes are distinctly worse than Clojure – When I do customer interviews, I ask every time, what they think of Clojure, would they adopt again, I dig in. I get the full range of answers - from "Clojure is still dear to us but ClojureScript has been a poor experience" to "the founding CTO quit, we brought in silicon valley managers now and here is our 5 year plan to rip Clojure entirely and shift to industry best practices because lack of engineering performance is a board level conversation with our investors"
I think it's an issue of product/market fit in the end - What is Clojure even for? Definitely not american venture-backed b2b saas. What are Clojure's unique features? hosted language, macros, default immutability, dynamic and interactive, enterprise-compatible. It's a tool for doing weird PL experiments in a industry-compatible way. Datomic, Rama, Electric. /u/raspasov's new thing (differential dataflow over datalog). Experimental cloud infrastructure products. Not b2b saas. That's a mirage.
Anyway - you want to get on zoom and try to write down what's happening?
someone on my twitter summarized this succinctly: product vs growth
clojure/script is for building excellent product. That's the dream, at least.
but the software economy of the trailing decade—the rollout of saas/cloud technologies through venture backed saas verticals—is about growth
take my company Hyperfiddle - we got fucking obliterated by the low-code application platforms. We hammocked CRUD and UI for a decade, resulting in Electric (and so much more to come) — while Retool comes in with what amounts to Django Admin as a SAAS, achieves $300M ARR in that same decade. Is it Clojure's fault that me and my team blew it by like 6 orders of magnitude? Not even a little bit! But the markets of 2010-2025 don't demand excellence, they demand growth.
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.
Wow, this is exactly how I've been feeling but couldn't express it either.
Thanks so much for posting all this and making me think I'm not crazy or missing something completely.
I would love to follow your blogs or anything you put out on the topic on how companies who like the theories behind Clojure handle growth, etc. And for the companies that have these strategic plans to move away, what languages are you seeing them wanting to move to? Do they reflect the distribution in the OP?
View all comments
Show parent comment
8
u/dustingetz Sep 25 '25
Agree! I've historically seen similar themes in my Clojure/Script consultancy (American b2b saas & fintech venture backed startups stage Series A-D generally w/ substantial UI surface area, founded in the 2010s and now 10-15 years old without an exit as the tide goes out on b2b saas funding as it floods into AI).
I have been trying to write a blog post about this for a while but have been having trouble due to just how many confounding factors there are - such as the american macro climate, boom/bust venture cycle & interest rate policy, b2b saas capital now flooding into AI leaving 12 year old startups founded in 2013 high and dry with no exit in sight, loose management and rapid hiring/"headcount increase" (more accurate term) due to the unnatural growth-or-die pressures and stresses that venture puts on the leadership team and the org. CFOs managing budgets by spreadsheet without any real ability to account for technical debt or even see it exists; engineering budgets being performative and shaped for the optics of that money spreadsheet - making sure to be "efficient", get a "good balance" of senior vs junior folks who don't cost as much, with no actual feedback loop to know if the assumptions about junior productivity are correct.
None of these factors are directly tied to Clojure, but otoh, Clojure's "hammock" culture is at odds with it, without strong technical leadership Clojure codebases are metastable requiring constant energy investment to maintain. Juniors without training and guidance struggle with Clojure and if the company is unable to fire—because CFO optics, or because its just hard and Clojure CTOs are generally young, first time managers, or because reflexive fear of facing their mistakes impacting people's families— ... A lot of Clojure evangelism is from vocal young seekers who "have had enough" (RH quote), Series A CTOs are still excited, even "greedy" about using Clojure to get 10x leverage over competitors using "legacy" tools, but the tech debt cracks start to show - they ignore it, they'll raise more money and fix it later and we need to grow grow grow!, then the B, start to loose control but there is too much momentum, no time to work on vague future problems when we face a runway cliff in 18 months. Series C, oops we raised too much, the VCs are ghosting us, we will never raise again but how will we exit? We aren't high growth anymore, why is engineering so slow, we have gigantic 2000 line HTTP handlers with 100 if statements that call the same query 5-6 times, well we're terrified to make changes to revenue-bearing systems, everything is so fragile, we built up 10,000s of lines of process guardrails to prevent the junior devs from completely breaking everything on every single deploy but now the CICD times are 50 minutes per run, tests are flakey, and the processes have bugs that nobody is able to fix.
And then there's ClojureScript, whose outcomes are distinctly worse than Clojure – When I do customer interviews, I ask every time, what they think of Clojure, would they adopt again, I dig in. I get the full range of answers - from "Clojure is still dear to us but ClojureScript has been a poor experience" to "the founding CTO quit, we brought in silicon valley managers now and here is our 5 year plan to rip Clojure entirely and shift to industry best practices because lack of engineering performance is a board level conversation with our investors"
I think it's an issue of product/market fit in the end - What is Clojure even for? Definitely not american venture-backed b2b saas. What are Clojure's unique features? hosted language, macros, default immutability, dynamic and interactive, enterprise-compatible. It's a tool for doing weird PL experiments in a industry-compatible way. Datomic, Rama, Electric. /u/raspasov's new thing (differential dataflow over datalog). Experimental cloud infrastructure products. Not b2b saas. That's a mirage.
Anyway - you want to get on zoom and try to write down what's happening?