I've been developing a library that wraps Clojure's collections for use in Java 8 development:
https://github.com/rschmitt/collider http://rschmitt.github.io/collider/javadoc/ Like my other major Java project, DynamicObject <http://rschmitt.github.io/dynamic-object/>, the goal here is two-fold: (1) Bring the best of Clojure to Java developers (without ruining it), thereby making functional programming easier and more familiar (2) Make the Clojure jar file as common as possible on people's classpaths, thereby lowering the bar to Clojure adoption I'd appreciate any feedback people have on the design: how things are structured, named, documented, tested, and so on. I haven't decided to stabilize the library yet, so there's still time for breaking changes to be made. Incidentally, the main project I'm aware of that's similar to this is clj-ds <https://github.com/krukow/clj-ds>, a standalone partial fork of Clojure. That also looks like a good approach to me, and fairly well-executed; it just has different tradeoffs. In particular, I like being able to target Java 8. I also like being able to wrap whatever version of Clojure is on the runtime classpath. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
