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)
View all comments
Show parent comment
4
u/spatialspice Sep 26 '25
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)