4 ms·
It's unfortunate that you got downvoted, because while people may not agree with this there is definitely something to this. My approaches to Clojure have been
by Daishiman 11y ago
It's unfortunate that you got downvoted, because while people may not agree with this there is definitely something to this.
My approaches to Clojure have been seriously hampered by the fact that some of the abstractions above those that are "simple" are remarkably complex, and that the tools that surround the ecosystem are still pretty frail.
Macro bugs are certainly something that have scared me away for a while.
- j-pb 11y agoMacros are for extending the language, I have never in 2 years of professional clojure dev, used a single macro in problem domain code. I've written a few libraries that are supposed to extend the language, but I've only used them rarely there too, maybe under a dozen times.
- Daishiman 11y agoSure, but when there's bugs in the caller of macros I have to figure out what exactly is going on, and that's where the rubber meets the road.
- mpdehaan2 11y agoYeah, exactly. My experiences were around looking for a quality ORM, job scheduler, and web framework - things like korma and ring exist - but they lack a large amount of features compared to equivalents found in /most other/ languages. I came to the conclusion that Clojure is an acceptable way to call Java SDKs if you want a bit higher Java velocity AND Lisp fits your brain already, but I'd rather pick up Scala or Groovy instead for that purpose. Libs in pure clojure, for which I tried dozens, were usually incomplete and error-prone even if they were community favorites, which I attribute in part to the fact that it's a small circle of developers using it, and the language is still newish.