So, i.e., they were struggling with just the stuff in Clojure that makes it a non-Lisp.
Those programmers should have been informed that there are real Lisps out there in which you don't have to do functional programming, and things are mutable.
So, i.e., they were struggling with just the stuff in Clojure that makes it a non-Lisp.
Those programmers should have been informed that there are real Lisps out there in which you don't have to do functional programming, and things are mutable.
Struggled to start with, sure. But ultimately for me those are the best parts. Immutability particularly. It takes a few weeks learn how to solve problems again but I do think it makes things simpler and removes a nice category of bugs.
Actually maybe Java interop was the best part. Without that I doubt we could have picked up Clojure. It's far less true today but this was almost 6 years ago. Back then knowing there would be a library, even if we had to quickly wrap it was essential.
I'm not defending a generalization against counterexamples by trying to exclude them with a moving-goalpost definition.
Mutation and pure procedural programming are part of Lisp. They are part of Lisp when they are bad, and part of Lisp when they are good. I've never shifted a definition of what is Lisp to exclude or include these characteristics in order to suit an argument at hand.