Clojure will affect the way you think about programming (2017)

182 points by sammatilda 18 hours ago on hackernews | 86 comments

darksaints | 16 hours ago

By a weird stroke of luck, clojure was one of the first languages I learned. And yeah, I guess it left a lasting impact on me in the form of an appreciation for immutability and dataflow programming.

Unfortunately it also left me with an extremely deep distaste for dynamic types, and in particular, the blind usage of lists and maps for everything. The ML family of languages finally gave me a paradigm worth keeping around.

quixoticelixer- | 16 hours ago

I started learning Clojure when I was 17, but then later moved away from programming. It's done the opposite with me, I struggle to really get the benefit of static types and I still think of everything as maps and functions.

Xirdus | 13 hours ago

The biggest benefit of static typing is that you automatically know every single operation you can perform on every single result of every single function ever made.

Tcepsa | 13 hours ago

Haha same! All you need are primitives and maps and lists and first class functions! (Though good decomposition syntax is up there as well; it can be really helpful for telling what a given thing needs the map to include!)

oblio | 12 hours ago

Awesome, how do you ensure clients of your code always do the correct operations on your data?

With static types it's obvious and you generally have to work hard (and in non intuitive ways) to mess up.

This becomes more important as team sizes grow.

skydhash | 8 hours ago

> Awesome, how do you ensure clients of your code always do the correct operations on your data?

Either the data type is opaque (as in you shouldn’t mess with it and you should use the provided api) or it’s just normal primitives and thus no restrictions.

You don’t usually reach into data structures to modify their properties, especially if it’s for foreign modules.

Kyo91 | 6 hours ago

I think an appreciation for static typing comes once you have to start working with code others wrote. I used to write a lot of clojure in my free time, but I think I liked it more because I was the only developer on those projects.

Working professionally in dynamic languages, especially those that use maps in place of objects/records, I would spend a lot of time trying to figure out which keys were present in various input maps. Were they always available or only sometimes? I could either add verify checks at function callsites or trace the map all the way through my code and hope it didn't originate from an undocumented API response.

A few years ago, we started migrating our code from Elixir to Scala. That involved a lot of work creating case class "schemas" for many records that used to be represented by maps. But now it's clear at dev time what data each function receives as input. What fields are required and which are optional. I can write a quick bugfix in a large module that someone else wrote without spending a full day tracing data paths and looking at runtime traces.

> the blind usage of lists and maps for everything

it's not blind, tho it could seem that way, and if someone hadn't thought deeply abut how they should use lists and maps, then it could be described as being blindly using them.

But this style is also what makes clojure dynamic, and flexible. Updates don't have to be rigid, and keeping backwards compatibility is a lot easier than a lot of statically typed languages.

That's not to say you can't have some rigidity where it's needed (specs for example, can be sprinkled in where you need/want it).

kmac_ | 12 hours ago

I always thought that a good craftsman knows many tools and techniques, so I learned and practiced everything. My goal was not to leave blank spots on my technology and language map. I learned FP, OOP, and various architectures like DDD, and I did not dismiss any language or major framework. "Every tool has its own place and is useful". Then, after years, I was employed by a company that used Ruby as their main language. "Such beautiful, simple code," I thought. It was a real culture shock for me. Strings and maps everywhere. No types. Monkey patching. No structure. I was really disappointed, but other words come to mind. I quit. So yeah. Once you go to some regions, there is no way back. I wonder how people who started with, for example, Haskell, and were shaped in a correct way, function when they touch other paradigms.

opiniateddev | 16 hours ago

fun fact: Conductor OSS has support for clojure

https://github.com/conductor-oss/clojure-sdk

Jtsummers | 16 hours ago

https://news.ycombinator.com/item?id=14928429 - One discussion from back then, 216 comments

TN1ck | 15 hours ago

There was a time in university where I started my days with doing some 4clojure puzzles. I became so obsessed, I managed to solve almost all of them. It's wild what an impact these few weeks had on my programming abilities. It's a beautifully designed language that makes you think in data structures and their transformations.

As a side note: I code Clojure in Lightroom. It was so cool to see your code instantly evaluate and trace through your functions.

xinuc | 11 hours ago

> As a side note: I code Clojure in Lightroom. It was so cool to see your code instantly evaluate and trace through your functions.

do you mean lighttable? or you really code in adobe's photo editor.

TN1ck | 3 hours ago

Sorry, meant Light Table, also meant past tense. It was cool back then.

sdeframond | 10 hours ago

Is lighttable still alive?

TN1ck | 3 hours ago

Sorry, typos all around, I meant that I coded (past tense) using Light table (not Lightroom :D).

xhevahir | an hour ago

This got me wondering if something like Light Table's instarepl would be feasible in DrRacket. I don't know how its GUI works but Gemini thought it would be amenable to vibecoding some of the features.

zergrush | 14 hours ago

Outdated article post-LLMs, if you are still taking to heart what this article says you are working against the trend.

You don't need any inner working of clojure or any lower language for that matter. It's all available within your reach. Don't let the people who have built an identity over the tools that they have chosen, they can't give you any meaningful advice anymore with what we have as tools.

I'm saying this as someone who has worked with clojure for over a decade. There is no point in gate keeping things anymore. It also means that the point of clojure which is supposed to have a lot of DX built into it , is gone with LLMs.

Software is largely solved now and the only thing that matters now is distribution so start thinking about your product and how to market it.

There was a good Conj 2026 talk on points that can make Clojure a great fit for LLM-driven development, same which make it convenient for humans also.

What tipped the scales for Clojure - Brendan Foote (Clojure/Conj 2026)

https://youtube.com/watch?v=tzzg8CVkl2A

Joel_Mckay | 14 hours ago

While I agree "LLM" have lowered the barrier to access languages, it is fundamentally just isomorphic plagiarism of around $9Tn worth of FOSS projects.

Much like how GPU were bodged onto the monolithic von Neumann CPU architectures, we may safely assume most "LLM" will be superseded by neuromorphic computing technology sooner of later. =3

zergrush | 13 hours ago

Viewing LLMS as compression is flawed because it shouldn't be possible to solve new novel problems. Zipping every single file in existence and then asking Winzip to produce a novel working zip file clearly doesn't work. Clearly LLMs are learning from data it is fed and a lot of what we do before LLMs also involved "plagirism". Even the greatest writers and artists would copy each other to master their styles and extract the dimensions. I think framing LLMs as compression is not only silly it demonstrates a poor understanding of the inner workings of LLMs

Joel_Mckay | 13 hours ago

Except a statistically salient search context is in proximity to something similar, and manual content curators drop their thumb on the scales weights to boost desirable outcomes in the quantized model.

https://www.youtube.com/watch?v=LPZh9BOjkQs&list=PLZHQObOWTQ...

The encoding of the LLM is almost always lossy compression, but we agree it is not real intelligence.

As a sentient turnip, I likely wouldn't understand such things, but do recognize copyright bleed-through when it includes known obscure works. =3

https://en.wikipedia.org/wiki/Mechanical_Turk

zergrush | 4 hours ago

Nothing in your video or sourced wikipedia support any of your claims, what is your exact argument that compression can solve novel problems without forcing readers to comb through the links that seemingly has nothing to do with the subject at hand ?

Joel_Mckay | 24 minutes ago

Did you actually know what the G.P.T. stands for in chatGPT?

Indeed, we shouldn't kink shame peoples cognitive dildo. =3

https://en.wikipedia.org/wiki/Sealioning

pitchlatte | 12 hours ago

> Much like how GPU were bodged onto the monolithic von Neumann CPU architectures, we may safely assume most "LLM" will be superseded by neuromorphic computing technology sooner of later. =3

perhaps this is the optimism i need today.

bigstrat2003 | 13 hours ago

> Outdated article post-LLMs

Outdated take post-slopocalypse. You still very much need to know how to program and will often get better results writing code yourself, as we have seen from the outages caused by people vibe coding shit.

> if you are still taking to heart what this article says you are working against the trend.

Being trendy is not synonymous with being correct. In this case the trend is stupid and making the profession worse, so one would be well advised to work against it.

> Software is largely solved now

If that were true, we would be getting a deluge of high quality software. Instead we are getting a deluge of crap. Software is by no means solved.

globular-toast | 13 hours ago

Even if what you say is true, I prefer to own my intelligence rather than rent it. Whatever makes you happy, though.

zergrush | 4 hours ago

Yeah? What have you accomplished and how do you plan on competing with LLMs ?

globular-toast | 35 minutes ago

The question sounds rhetorical and quite offensive, to be honest. But to answer, I've accomplished loads and nothing can take that away from me. I don't plan on "competing" with LLMs, I just don't plan on losing my own intelligence and relying on AI companies for it.

Ampersander | 12 hours ago

You're absolutely right! It's all in the title really, Clojure can't affect how we think about programming anymore, because we stopped both thinking and programming.

acobster | 6 hours ago

Point taken—you're right to push back on that.

zergrush | 4 hours ago

I see you think that using LLM can replace critical thinking and you reject a tool based on that flawed assumption.

AnonymousPlanet | 8 hours ago

There are those who are content to have the LLM do their homework and never bother to understand the solution because "it's solved".

But they will be overtaken by those who use the LLM as a sparring partner to form their own understanding and elevate themselves.

I fear we will see a huge disparity between both groups. One ever on the rise while the other is left in the dust.

zergrush | 4 hours ago

You forgot the group you clearly belong to: The one that will not adapt to new tools and innovation

AnonymousPlanet | 3 hours ago

I don't think you have any idea what group I belong to.

acobster | 6 hours ago

I feel sorry for people who feel like they have to give up on thinking about programming. That sounds so boring.

zergrush | 4 hours ago

Has nothing to do with LLMs

jonjacky | an hour ago

I don't understand the motivation of these people, frequently seen on HN, who burst into discussions of programming to say that programming is over. Can they really think that the people they rebuke are unaware of the technical developments in the last several years?

They sound defensive and insecure, which I suspect is not the impression they are trying to create.

stephbook | 14 hours ago

I think clojurists overestimate how advanced their language is. Or maybe it's just my outsider's perspective? Famously, Clojurists/Lispers think that theirs is the most advanced language and everyone who fails to see that just doesn't understand expressive power.

In any case: Typescript has dynamic types and static types, it has true union types, it has hot reload (what you might call REPL), it has the widest package ecosystem and so much more. It works out of the box with the most popular IDE and you don't need to learn emacs.

I rarely hit the power ceiling of Typescript, so I never put in the work to learn Clojure.

confluent persistence, on data. which changes how you think about concurrency.

it allows you to "branch, work on a worktree, and merge" but unlike git worktrees you don't need to copy a complete clone of the data, you instead, like in the git object store, share most of it and only need memory for what you touch in your branch.

and your data only changes when _you_ decide to rebase, and merging partial work results is a _deliberate_ step, not something happening under your feet.

layer8 | 7 hours ago

How are merge conflicts handled in Clojure, in that picture?

acobster | 6 hours ago

Latest one wins. But you can keep a reference to the old, unchanged structure around, too. This is why immutability is important.

``` (let [a {:greeting "hello" :name "world"} b (merge a {:greeting "hi"})] [(:greeting a) (:greeting b)]) ; => ["hello" "hi"] ```

quixoticelixer- | 12 hours ago

I don't think I've really seen the argument that clojure is "advanced" much at all.
Typescript doesn't have a real repl. You cannot redefine just one variable in a running program and have the rest of the compilation untouched, yet aware of the redefinition.

I get that "hot reload" can feel similar, but it's not the same and is more limited for debugging, experimentation, extremely fast (sub-ms) iteration loops, etc.

Another thing you can't do is running/debugging tests without triggering more compilation. In a real repl language you drive things in-process, not from the outside with compilers and test runners.

Typescript is lovely btw, just have a go at other paradigms if you feel like it.

bcrosby95 | 11 hours ago

Fuck being advanced, I love how stupid simple it is.

dyzone | 6 hours ago

Javascript is the peak of programming language design, unironically.

ajasmin | 14 hours ago

I love the thoughtful approach to programming that Clojure exemplify.

MVP churn and AI fatigue is getting to me. Need some good Hammock Time!

deterministic | 13 hours ago

If you enjoy your brain exploding then I also highly recommend learning LEAN and how to prove software correct.

theanonymousone | 12 hours ago

To me, Clojure was "Lisp for JVM". Is that an incorrect picture?

I mean, recently I saw Clojure for . Net and Clojure without JVM (forgot the name). If you don't need/want JVM, then why would you use Clojure over e.g. Common Lisp?

quixoticelixer- | 9 hours ago

It used to be tied heavily to Java and then JavaScript but it's on quite a few platforms now. But clojures big thing is dynamic functional programming, passing immutable maps to functions.

podgorniy | 8 hours ago

Common Lisp was designed to unify several Lisp dialects. Its standard reflects historical compromises, but it also deliberately supports several programming styles.

Clojure makes stronger choices about the default style: immutable data, transformations over collections, and explicit tools for managing changing state.

Zooming out you're right: it's lisp and jvm is a difference. Zooming in and there are different ergonomics and incentives on how to structure the program.

dapperdrake | 3 hours ago

A little bit.

Clojure is a lisp-1 which, surprisingly, feels better to use than a lisp-2. Much more intuitive. (You can kind of also have a function call returning a function in the first position of a list and it just works. Common Lisp doesn’t like that at all and you need funcall or apply.)

The immutable data structures and better array and hashmap syntax and ergonomic hashmap argument destructuring remove a lot of mental overhead. Kind of like Python or JSON-in-Javascript.

Having slight syntax variation like square brackets for let bindings and one less level of nesting in let bindings makes it easier to read. Still homoiconic, though. So you get the best of both worlds.

The hygenic macros helped me design better anaphoric macros.

EDIT: typo

dapperdrake | 3 hours ago

Clojure and hylang (python) help with understanding threading macros (-> …), so basically more readable shell pipelines.

Hylang also had a good take on anaphoric macros in relation to threading macros. Clojure makes it more obvious that explicitly passing in the anaphoric symbol at the call-site is better for maintainability. This offers threading with arbitrary argument positions instead of forcing first or last position.

Clojure transducers finally broke the ice on common lisp series. The CL side of this is horrifying. SBCL seems to have dropped its sb-series contrib module. But it moved us far enough along that we now have parenscript-series. So upside all around.

Don’t know enough Fennel (Lua) or Elixir (Erlang) yet, to have any useful comments there.

There are other Lisps for JVM such as ABCL and Kawa.

sourdecor | 12 hours ago

I recently found out you can use Malli type providers[0] with Typed Clojure[1] to get instant feedback when developing!

So you can do this when programming:

  (m/=> foo [:=> [:cat :int] :int])
  (defn foo [t] (inc t))
  (foo 1)
[0]: https://github.com/typedclojure/typedclojure/tree/main/examp...

[1]: https://github.com/typedclojure/typedclojure

tikotus | 11 hours ago

In the era of LLMs, I often stop to think of Clojure. I believe it had a significant role in popularizing the concept of immutable data structures. Immutability simplifies the required context for understanding and solving problems. This benefits both humans and LLMs.

Would an LLM, or a person solely coding using them, have had the insight to work out that immutability is the way to go, and we should revolutionize software develoment? If LLMs had happened 15 years ago, would all code still be "place oriented programming", with higher token counts and less reliability than we have today thanks to better practices we've learned in the recent past?

If so, what are we missing out on in the future, now that stopping and thinking about code is frowned upon?

stingraycharles | 8 hours ago

Aren’t these abstractions mostly meant to make reasoning about code easier for humans, and wouldn’t LLMs optimize for easy reasoning for LLMs?

Phrased differently: what would a language look like that’s optimized for LLMs?

tikotus | 8 hours ago

That's a good question. I do think that for example immutability is easier for LLMs as well, since it reduces the required amount of context for any give part of the software. But there might be even bigger wins out there for LLMs.

Is anyone out there trying to find these wins?

stingraycharles | 8 hours ago

Well answering my own question, but I think a strong type system with clear error messages is extremely useful for an LLM.

Just look at how a system like LEAN allows LLMs to incrementally solve a problem. It absolutely wouldn’t get that far if it couldn’t rely on some type of compiler to verify things.

So yeah, a strong type system that allows lots of constraints to be expressed easily.

I think Haskell and Rust are much more “LLM-compatible” than Clojure.

And I say this as someone who has written Clojure full time for over half a decade.

tikotus | 7 hours ago

Oh, absolutely. LLMs thrive with problems that are easy to verify. They don't always get it right, but the number of attempts they can do in a short time more than covers for it if verification is fast. Type systems are great for this.

layer8 | 7 hours ago

This comes down to the question of how much LLM reasoning differs from human reasoning qualitatively. Maybe for the most part reasoning is just reasoning, so most things that help for human reasoning also help for LLM reasoning, and vice versa.

brlewis | 8 hours ago

>If so, what are we missing out on in the future, now that stopping and thinking about code is frowned upon?

You're probably asking this rhetorically, but if you were seriously asking, this would be one of those riddle sentences like "This sentence is a lie." If somebody had an idea that they could articulate in natural language on this forum, the natural language would be something an LLM could process and turn into better code. Any true answer could make itself false.

What we'd miss out on if stopping and thinking about code was no longer a thing, would be ideas that stem from direct human experience. Language models relate words to words. There's a lot of power in that, way more than one would think, but they don't relate words to direct experience, except as described in other words. Innovation comes when humans express their direct experience in new natural language, that other humans can benefit from, and eventually language models benefit from.

Clojure and Elixir both do really well in the LLM age. Functional programming in general, but those two in particular as they have a runtime/shell that agents can interop with directly to view/modify the code as it runs.

I actually just wrote about doing more clojure a few days ago

https://tuhat.net/@sbr/p/beam-to-jvm

phplovesong | 6 hours ago

We had immutable data LONG before clojure was a thing. Immutability is good, but nothing new, ir nothing that should be forced.

tikotus | 6 hours ago

You're right, but I wouldn't nullify Rich Hickey's hard work just because he didn't invent persistent data structures. He's done much more to the industry than just created a language. My question is, will we have more people like him in a world where people no longer spend hammock time thinking about code?

wavemode | 6 hours ago

> If LLMs had happened 15 years ago

Functional programming and immutable data structures are much older than Clojure

> If so, what are we missing out on in the future, now that stopping and thinking about code is frowned upon?

"We" here is vague. In truth, the vast majority of programmers just use whatever is most convenient at their place of work and do not participate in, nor care about, the advancement of the craft. That has always been true.

I imagine that, as we enter an age where many programmers don't even read code anymore, those people will largely stop caring about programming languages and paradigms entirely. But, a few will still have to. Similar to how most programmers nowadays don't think about allocation and memory management, but a few still have to.

tikotus | 5 hours ago

You're right that Rich Hickey didn't invent functional programming or persistent data structures. But he did a lot to advance the industry. I'm not saying it's solely thanks to him, but immutability is now the default in many places, which definitely wasn't the case 15 years ago.

And Rich didn't do what he did because he had to do it. He risked his own savings to go on this crusade, to make software development a happier place.

Who will take a risk like that in a world where no one writes code?

wavemode | 3 hours ago

there will always be people who write code. just like there will always be expensive handmade goods, even though most goods are mass-produced in factories nowadays.

keybored | an hour ago

At this point I often just pop into real tech threads (using tech with your own hands) to see how many But Now In The LLM Era top-level comments there are. And whether they follow the template of “now that there is <outcome I have asserted>, what philosophical ramifications does that have?” (For who? The humans that are not there?)

There’s where my reading habits are right now. I guess well played?

shevy-java | 9 hours ago

So, people say this about programming languages all the time.

My problem is:

a) this assumes that people can not have ideas without a programming languages. That's obviously incorrect. I can have ideas without knowing a programming language.

b) languages also constrain the thinking. For instance, in ruby you have a class and a module, as distinction. Is that a useful distinction? I think it is overlapping, with modules giving more flexibility. In practice, this distinction does not lead to many problems, but if you have: class Foo; module Bar; end; end and then you were to write "class Foo::Bar" in another file because you want to modify the code quickly, then ruby says you'd have to use "module Foo::Bar" instead, because the ruby parser already knew that this is a module, not a class. It is not a big problem, but whenever I run into this issue, I wonder why I need to care whether it is a class, or a module. Because, when I do so, such as adding a new method to that, perhaps from another namespace/project, then I wonder why ruby does not prioritize me wanting to change the code, but instead complains about that it is a module or a class. (I understand the ruby parser has to work that way, in order to differentiate between errors made or mixing up code, but my point of contention here is the "class versus module" distinction. The above is one example of many more that can be found in programming languages.

Of course you can reason that better programming languages typically lead to better implementations too. I'd reason in favour of such a statement. I don't really see the point of learning a language that is inferior to languages I already know, when I know I am not going to use that language. The "learn a new language every year" is not a bad idea, but why would I want to learn languages that are bad? That makes no sense. There is competition between languages, as well as against time.

cryptopian | 8 hours ago

> languages also constrain the thinking

Which is precisely why trying out languages built on different paradigms is a good way to widen the way you think about programming.

lioeters | 6 hours ago

This is equally true of human language as well. Learning a new language expands the mind and often allows you to think new thoughts that weren't possible or intuitive in other languages.

meken | 8 hours ago

This year has been fun for learning programming languages that change the way I think. The highlights have been:

- Clojure for functional programming (you mean you can update a bitmap in a purely functional way??)

- Array langauges (APL, BQN, J) for avoiding loops with matrix operations

- Prolog for avoiding loops with backtracking

podgorniy | 8 hours ago

The interesting thing about Clojure, for me, is that for all its beauty and power, it’s so simple that there isn’t much variety in the articles you can write or the “gotchas” you can cover for a wide audience. Niche stuff that assumes you already know Clojure doesn’t catch on with a wider audience. Its strong points—“everything is data,” “REPL development,” “immutability and strong primitives,” and “paradigm shift”—get repeated so often that they become noise people just filter out.

There isn’t much room for yet another framework or another way to work with data (I’m looking at you, Node.js), so there isn’t much to talk about or write articles about.

In other words, the efficiency and simplicity of the language act as a barrier to its spread in a world where only repeated mentions get through. IDK, maybe this is for the better after all.

It's an interesting question, even outside programming.

Before people might ask questions and discuss things on obscure forums or subreddits. Now that LLMs are trained on all this data people no longer need to do that.

You just ask and LLM and get a throwaway answer that people generally trust as the best option.

Where do the new insights and opinion come from? Especially when LLMs start getting trained to recommend certain products.

eddiewithzato | 7 hours ago

We don't do that anymore. I mean FP is just natural language now, can't wait for LLM optimized languages. I don't read the rust/ts code produced by claude anymore, so why bother using said language.

mdnahas | 7 hours ago

I’ve used Clojure a bit. Really liked it.

If you want to dive into Lisp, read Paul Graham’s book “ANSI Common Lisp”. It will show you the “why” and the concepts. Then learn Clojure for the syntax.

Even if you can never see yourself programming with Lots of Silly Parentheses (LiSP), the book is worth reading for the concepts. (And to imitate his writing style.)

For the outsiders the meme is that it's full of parens.

For the insider the meme is that it's the same parens: instead of `function(a, b)` you move the open paren to the beginning: `(function a b)`.

Immutability is a much bigger hurdle for most newcomers.

Anyway I recommend trying out Clojure and enjoy.

embedding-shape | 2 hours ago

> If you want to dive into Lisp, read Paul Graham’s book “ANSI Common Lisp”. It will show you the “why” and the concepts. Then learn Clojure for the syntax.

Kind of feels like if someone never been exposed to Lisp before, not sure if they'd like it or not, "Hackers and Painters" (by the same author) is a better (non-technical) introduction to the "why's" of lisps. Less of a manual and more "high-level" about creative work in general.

mdevere | 6 hours ago

This Or Jai! If you can get access.

nlitened | 6 hours ago

The more I work with Clojure, the more I am amazed how well thought-out, practical, and forward-looking it is, how well all its parts play well together.

And now, when I write all the code with agents, Clojure helps immensely with aligning agents’ code with what I want, with making sure I fully remain in control of all important behaviors of my code, with testing the agent-generated code, with troubleshooting running systems. Which probably means that Clojure is focused on delivering flexible complex production systems in general, not just human programmers’ ergonomics.

I try to use Rust whenever I can for small projects, but if I expect the system to be complex, I just have write it in Clojure, otherwise it would quickly get out of my control, and lose in performance and simplicity.

netbioserror | 6 hours ago

And it did. Clojure and Rich Hickey helped me understand that the most basic units of computation, data and functions, really are the simplest and most general-purpose tools for thinking about and modeling problems.

The programming books from my youth and my classes in college were so completely invested in Java and OO (from page 1) that it's only with hindsight that I can recognize: They never EVER gave a motive for why solutions need to be modeled that way. It might've been something like "We don't have enough memory or CPU throughput these days to be constantly copying data and performing collections", but even that is just an argument for procedural programming.

ertucetin | 3 hours ago

Lisp is something people just can't seem to kill. It refuses to die. I know it's a niche language, and it will probably stay that way. But if you look closely, Lisp posts frequently make it to the front page, especially Clojure posts. They're always popping up now and then, attracting lots of comments, just like this thread.

I've been a Clojure developer for over 10 years now, and this still surprises and thrills me.

mlmonkey | 3 hours ago

Each of these 4 families of languages: Prolog, Lisp, ML, C/C++ will affect how you think about programming, each in their own different way. Most of us do imperative programming (C/C++) and are content with that; but if you really want to expand your thinking, try languages like Prolog and Lisp.

jonjacky | 2 hours ago

I strongly recommend Hickey's own long essay on his experiences and thinking that led to Clojure, and his explanation of the most important features of Lisp in general and Clojure in particular. He wrote it for the 2020 ACM HOPL history of programming languages meeting:

A History of Clojure by Rich Hickey https://dl.acm.org/doi/pdf/10.1145/3386321

Rich Hickey's talk from this year:

https://youtu.be/P5eO7BNyJao?si=45zxrLUsY9AMUg6B

I feel like there was not enough fuss about what he showed off this year considering how many programmers (historically myself included) cared about checking/enforcing structure on a potentially nested thing, spec in usage has proved to be good for external boundaries but not great for internals

I remember we used to code something like:

class User { name age username password }

etc all the time but would end up having to make everything optional so that we could use the type hint against the age method and the auth method when we had partial information for the object

Obviously not an optimal design and can be broken down into yet more types and then composed together but I'm not a huge fan of object of object of object type situations — anyway my point is that Rich showed that we can just do the checks in context using deconstructing and in a reusable way rather than trying to declare a type once centrally and then cram that into everything else

I haven't explained it very well — I wanted to do a blog on it but just watch the video its one of the few things I got excited about even though I don't really code directly any more - the sad thing is current LLMs won't even use the technique because its not in their training sets and that still matters I've noticed for what they do