Chouser <chou...@gmail.com> writes: > ...except of course that every external dependency is an increased > burden on the users of any code I write. It seems likely that a > pretty substantial percentage of use cases could be handled in a way > that would allow either Java lib to be used underneath. That way I > would have no extra dependency now, or if I need Joda features could > use that instead.
This is exactly how I feel. Relying on code in contrib is no big deal, but as soon as I read something about downloading an external jar file and making sure it's on the classpath, I start to rethink whether I *really* need that functionality in the first place... maybe I could just wrap something built-in to the JVM. So why not start with that in the first place? If Joda gets included in the next JVM, that would be great. If a good package manager that could automate these kinds of dependencies were written and achieved wide use within the Clojure community, that would be even better. But we need to consider the current situation. There's definitely a need for The Simplest Thing That Could Possibly Work. -Phil --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
