Are dependencies the potential problem, or are "utility belt" dependencies the issue here?
If its the latter, then should we be trying to break down the utility belt into groups of related functionality, which can be stable and focused. Promoting zero-dependency libraries just means re-inventing a bunch of wheels, I believe node.js has this right by making dependencies cheap and easy and promoting publishing reusable libraries with only a few functions in. Not being able to load multiple versions of the same dependency make this slightly harder, but the general goal appears to me to be a good one. Glen -- -- 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/groups/opt_out.
