On Sep 10, 9:31 pm, Sean Corfield <[email protected]> wrote: > On Sat, Sep 10, 2011 at 9:46 AM, Jan Rychter <[email protected]> wrote: > > If you use Clojure to build an application that you subsequently > > launch and maintain, it is pretty much a given that you use contrib. > > Lots of it, in fact. > > I think that depends on when you started building stuff with Clojure. > I get the impression quite a bit of old contrib grew up to provide > functionality not in Clojure's core and I see quite a few pieces of > old contrib that are explicitly deprecated because functions moved to > Clojure 1.2 (c.c.string, for example, mostly moved to clojure.string > long before Clojure 1.3 got under way). I suspect that folks who > started with Clojure long ago and are relying heavily on old contrib, > are probably relying on those old deprecated namespaces and functions > and have simply avoided updating their code to use the newer, > supported namespaces. I think the break in contrib coming with 1.3 > will be good for the Clojure ecosystem overall because it will force a > lot of folks to clean up their code :)
Just to clarify, I am not against change, quite the opposite — I'd much rather see a quickly evolving Clojure ecosystem than one mired in legacy code. I will gladly rework my code regularly so that it works with newer releases. I'd just like to see the process somewhat documented. I think I've said all there was to be said in this discussion, so I'll shut up now and wait for better documentation or a migration guide. In the meantime, we'll stick to Clojure 1.2 together with our patched-up monolithic contrib. thanks, --J. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en
