> Outlawing custom abstractions in favour of a few very shallow ones doesnt seem like a convincing thechnical argument. The entire point of the Lisp Curse is t

> Outlawing custom abstractions in favour of a few very shallow ones doesnt seem like a convincing thechnical argument. The entire point of the Lisp Curse is that this is a social issue! Not a technical one. And, furthermore, what is a technical issue in another language can be pushed into being a social issue in a Lisp. And social issues are a lot more difficult to solve. Compare this to something like Java + Spring Boot or Ruby on Rails or any other framework favoring configuration and convention over code. Where the explicit point is a social agreement on what a program looks like, which in turn allows everyone to hopefully focus on the actual business logic. (Also: Sibling commenter already addressed the differences in abstraction power better than I would have.)