If you maintain some discipline in your engineering process, then there's very little risk due to the specific library (and if you don't keep a high level of discipline, then you're finished before you start).
- Test the h*ll out of everything. If there are bugs in Clojure that affect you you'll find them just as if they were bugs in your own code. You could look at Clojure as just another Java library with the JVM being the base technology. - Don't let people use arbitrary versions of Clojure and Java (and Contrib, if you'll use it). Pick one, package it with your project, and then leave it alone. If your code works, you don't need the latest version of Clojure. If there's a feature or patch you need that requires an upgrade, do a full regression test. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
