2 ms·
This is why I’ve found myself doing Clojure for everything. Clojure has its own pretty-ok ecosystem, but also benefits from the Java ecosystem, while still givi
by tombert 4y ago
This is why I’ve found myself doing Clojure for everything. Clojure has its own pretty-ok ecosystem, but also benefits from the Java ecosystem, while still giving me some lispey goodness.
Granted, sometimes the mixing of paradigms can kind of clash, and that’s its own can of worms, but at least I never get that “ugh I could have done this with a library in <language X>”
- mmcdermott 4y agoWhen I reference Java from Clojure, I usually wind up with a thin layer of wrappers around the part of the library I need to make the main codebase feel more properly Lispy. It isn't perfect with the different mental models between the languages, but it helps.
- tombert 4y agoYeah, and I think wrapper functions are fine and normal. The part that I do find annoying is when I have to break out macros to make my wrapper usable. When I was using the Java bindings for Apache Spark a few years ago, I felt like I was constantly reaching for macros to do some clever stuff, which is no fun.