On Sat, Jul 30, 2011 at 10:58 AM, Mark Rathwell <mark.rathw...@gmail.com> wrote: > > I'm all for a better, easier solution that is better in most ways. What I'm > saying is: > 1. I don't want to go back to downloading jar files from the websites of all > of the libraries I want to use in a project and tracking different versions, > no matter how large or small the project is, as suggested in your OP. I > think the centralized lein/clojars/github is an improvement over that in > almost every way.
"Almost" being the operative word. One distinct disadvantage is that it makes building your project require a working network connection and depends on single points of failure in Clojars and Github. So, network or site outages can delay your own work. Also, development under this model would be difficult on a mobile platform (such as a netbook) whose internet connection is flaky (e.g., up only when there is a free WiFi hotspot within range) or expensive enough to turn off most of the time (cellular data networks). (And both WiFi and cellular are subject to flaky signal strength depending on local conditions, too.) > I really think incremental improvements to lein/cake/etc, over time, will > yield better results than going back to square one. This is probably true, even given the above issues that can arise with a build process that presumes reliable 24/7 network connectivity. -- Protege: What is this seething mass of parentheses?! Master: Your father's Lisp REPL. This is the language of a true hacker. Not as clumsy or random as C++; a language for a more civilized age. -- 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
