On Feb 23, 2011, at 4:06 PM, David Jacobs wrote: > > - better discovery for existing, well-tested libraries. > > You can search on http://clojars.org/. This works well for me. > However, the key to well tested libraries is having people give > feedback if a library breaks or is badly documented or doesn't meet > their needs. > > To me, Clojars is not the most discoverable interface in the world, though I > do appreciate that it exists. It doesn't have download counts or any other > sort of quality indicator. What's more, some entries are domain-qualified and > others aren't, and it's hard to know exactly what I'm getting when I install > any package from Clojars.
I've never quite understood the criticism that it's difficult to find Clojure libraries -- perhaps because I came primarily from the Java and Python worlds, both of which share the same library-discovery mechanism (i.e. Google). That said, of course it'd be great to have a top-notch directory (and it looks like various people are working on that). In any case, this isn't relevant to the language's versioning. > Side question (also relating to the ecosystem feeling rough), what's with all > the "SNAPSHOT"s on Clojars? Clojars provides only one repository, where both SNAPSHOTs and releases are deployed. AFAICT, few people understand what SNAPSHOT implies, and the importance of having sane releases (i.e. a non-SNAPSHOT version as well as having no transitive SNAPSHOT-versioned dependencies). It's an unfortunate state of affairs. Cheers, - Chas -- 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
