Too fragile. This reminds me of the notion of "situated programming", featured in the talk by Rich Hickey: you and your programs operate in the middle of a bizarre and changing situation. For Clojure, the Java ecosystem is part of that situation. Even if some jars do not overlap today, you will be forced to take a minor update someday that introduces a clash. Or perhaps (quite likely) jars do overlap today, but you will take a minor update someday that causes the classpath to emerge from the hash-map differently and your program won't work anymore. The insight of the theory of "situated programs" is, not to hit a cliff when a perfectly legal quirk arises in the situation.
> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/clojure/4005f2c2-d95d-4612-b2e3-b223b731700eo%40googlegroups.com.
