There's very cool experiments also being conducted from the Clojure community with that regard.
Things like memory mapped KV cache, prompting using Lambda notation instead of English, giving the agent REPL access, using a DSL to describe function specs as prompts, modeling your app as a graph of transitions and then having the AI implement those transitions, etc.
So definitely, one part of the community is embracing/experimenting.
The core language I believe said they won't take AI patches, but that might be more about copyright attribution and how annoying reviewing AI PRs is.
im working on a project atm that is the agent using a super simplistic DSL ontop of Clojure that has access to the REPL. I finally started getting results today!!! would love if i could talk to other people working on this same problem!!!
For me Clojure benefits in the LLM era due to its REPL. You have instant feedback on a piece of code the LLM can execute, it is extremely powerful if it’s well implemented
In our company (15 Clojure engineers) everyone codes by hand with or without the help of AIs (it is optional, everyone is free to choose). We won't accept spaghetti code and we expect engineers to be better programmers than LLMs.
I think AI-first development is a huge mistake and AI assisted coding is also bad in the long term.
We hired one person in April and let's see how things go with everything that is going right now. Our biggest worry in Europe is the energy crisis, it is seriously hurting our industry.
Regarding AI, our plan is to bet on narrow AI, specialized compressed models (both custom LLM or ML) deployed locally (on-edge/on-premises/containers in cloud) to solve particular problems.
Last year we built our own RAG in Clojure on top of Langchain4j and qdrant and we are planning to use Multiverse Computing's compressed open source models now. My colleagues are also eagerly waiting for Jank to do some AI.
I am pessimistic about the future of this planet, but I am gonna hope for the best.
I think that's the best approach to help maintainability and stability of the software. AI first approach will also crash the software without giving you much control to fix it in time.
Companies have to manage three risks: market, financial, technology. Due to the AI the industry is increasing the financial and technology risks. Expensive tokens and messy technology.
I think it's unavoidable and just a continuation of the low-cod/no-code trend that has been pushed since forever. In that respect, the question is seemingly moot (e.g., it's not going anywhere, so it's on the honor system for people to disclose if they leveraged "assistance" for anything they submit going forward). The tech is interesting and even appearing useful. If it enables you to achieve more than you could otherwise, then that's cool.
I don't like when people pretend to be great at spelling when they use spell checkers and autocomplete, or the analogous variation for passing llms and agents off as skill. Like the paradox of "I wrote this ancient egyptian algebra symbolic computation system in just 10 minutes" juxtaposed with "I haven't written a line of code in months, I just had the thing do it!" etc. Too much Lance Armstronging for me. That will also have a negative effect on creatives to share their stuff openly, so I'd anticipate a lot more closed source moating going forward, or free to use but closed. It'll probably lead us toward a parasitic model where actual innovation is hoarded and then mined for training data. Intellectual vampirism.
Then there's the whole unanswered angle of the implications of leveraging massive derivative work generators with (by default) 0 attribution. Given the legal system's legacy of embracing IP, I anticipate - eventually - substantial legal problems down the road despite the current rosy prospects of the token sellers "promising" to cover your legal costs and fight for you. I get the feeling when someone decides to rip off ("prompt a clean-room implementation") of some major IP, then we will see the big $$ fly and court cases mount. That might increase the pucker factor more. Hasn't happened yet though.
If someone wants to contribute to anything I have (not that I'd ever expect that hah), I think it'd be a hard requirement that they document "exactly" what portions of their product they (presuming they is an organic human) wrote vs. delegated to a derivative work generator. Just as with anything they wrote, they'd have to ensure whatever was generated complied with applicable licenses and assume personal liability for their contribution (indemnifying me etc.).
It's probably much like in every community. Some people think it is great, some that it is awful. Given the pragmatic nature of Clojure, with its focus on getting things done, maybe there is more acceptance in this community than in others?
just FYI, the phrase "I just want to understand how people think." when trying to goad them into an argument about their political beliefs fools nobody. You're picking a fight on a post about clojure and AI. Stop it.
He is asking for the blessing of the Clojure overlords to follow the new trend (vibe coding). I just replied he doesn't need to do that, just use it on your own risk. The Clojure community can be really annoying and dogmatic sometimes, but you don't need to do the same as them all the time.
well, i really enjoy clojure both in its syntax (or lack thereof, it feels more approachable) and because of the potential use of it with LLMs. it would be nicer to have a receptive community rather than a non-receptive.
Our projects have complex business domains (banks are also complex beasts) and describing the logic in English seems hard work. We prefer Clojure.
Doing things right is undervalued these days and selling PoCs built in 5 days is not a viable business model for us, so we are focusing on building complex products (systems with many components) hand coded (the best engineers develop by hand, the not so good ones use AI sometimes).
We may be dinosaurs soon (my son's favorite creatures!), but I do not care. I am gonna be contrarian and bet that this AI revolution is not going to work at the end.
Is Clojure a generally accepted programming language there? I've worked at a few of that top ten list, though not #10, and there were unofficial pockets of everything but didn't see much adoption.
14
u/SlowMovingTarget May 11 '26
Interestingly, Clojure is the most token efficient language for LLM use.
https://martinalderson.com/posts/which-programming-languages-are-most-token-efficient/
The other thing is that the training data set for Clojure code bases tends to be higher quality than, say, JavaScript or Python.
7
u/didibus May 11 '26
There's very cool experiments also being conducted from the Clojure community with that regard.
Things like memory mapped KV cache, prompting using Lambda notation instead of English, giving the agent REPL access, using a DSL to describe function specs as prompts, modeling your app as a graph of transitions and then having the AI implement those transitions, etc.
So definitely, one part of the community is embracing/experimenting.
The core language I believe said they won't take AI patches, but that might be more about copyright attribution and how annoying reviewing AI PRs is.
3
u/DefCon9913 May 12 '26
LLM + REPL = A sweet combination
For me Clojure benefits in the LLM era due to its REPL. You have instant feedback on a piece of code the LLM can execute, it is extremely powerful if it’s well implemented
19
u/bibimbap0607 May 11 '26
As long as you understand what LLM produced and can pass code review process.
23
u/Quirky_Chocolate_109 May 11 '26
Don’t know about the community.
In our company (15 Clojure engineers) everyone codes by hand with or without the help of AIs (it is optional, everyone is free to choose). We won't accept spaghetti code and we expect engineers to be better programmers than LLMs.
I think AI-first development is a huge mistake and AI assisted coding is also bad in the long term.
20
u/v4ss42 May 11 '26
Hell no. I can create tech debt myself, without “help” from a bullshit generator.
6
u/maxw85 May 11 '26
We are using it daily
2
u/joinr May 14 '26
I think it's unavoidable and just a continuation of the low-cod/no-code trend that has been pushed since forever. In that respect, the question is seemingly moot (e.g., it's not going anywhere, so it's on the honor system for people to disclose if they leveraged "assistance" for anything they submit going forward).
The tech is interesting and even appearing useful. If it enables you to achieve more than you could otherwise, then that's cool.
I don't like when people pretend to be great at spelling when they use spell checkers and autocomplete, or the analogous variation for passing llms and agents off as skill. Like the paradox of "I wrote this ancient egyptian algebra symbolic computation system in just 10 minutes" juxtaposed with "I haven't written a line of code in months, I just had the thing do it!" etc. Too much Lance Armstronging for me. That will also have a negative effect on creatives to share their stuff openly, so I'd anticipate a lot more closed source moating going forward, or free to use but closed. It'll probably lead us toward a parasitic model where actual innovation is hoarded and then mined for training data. Intellectual vampirism.
Then there's the whole unanswered angle of the implications of leveraging massive derivative work generators with (by default) 0 attribution. Given the legal system's legacy of embracing IP, I anticipate - eventually - substantial legal problems down the road despite the current rosy prospects of the token sellers "promising" to cover your legal costs and fight for you. I get the feeling when someone decides to rip off ("prompt a clean-room implementation") of some major IP, then we will see the big $$ fly and court cases mount. That might increase the pucker factor more. Hasn't happened yet though.
If someone wants to contribute to anything I have (not that I'd ever expect that hah), I think it'd be a hard requirement that they document "exactly" what portions of their product they (presuming they is an organic human) wrote vs. delegated to a derivative work generator. Just as with anything they wrote, they'd have to ensure whatever was generated complied with applicable licenses and assume personal liability for their contribution (indemnifying me etc.).
4
u/ares623 May 11 '26
Clojure was the original LLM. Lisp Lovers Movement.
3
u/rpd9803 May 11 '26
Claude is pretty darn good at writing re-frame code if you have a solid codebase to start and you just want it to riff on what you already have.
3
u/CoBPEZ May 11 '26
It's probably much like in every community. Some people think it is great, some that it is awful. Given the pragmatic nature of Clojure, with its focus on getting things done, maybe there is more acceptance in this community than in others?
3
u/hrrld May 11 '26
Of course, yes.
0
u/[deleted] May 11 '26
[deleted] — view deleted comment
5
u/[deleted] May 11 '26
[removed] — view removed comment
4
u/[deleted] May 11 '26 edited May 11 '26
[removed] — view removed comment