> Another thing to look at (there's always another thing to look at) this worries me... it is sorta like the discussions i see about how some new db engine is FAST, oh but it totally fails on occasion and trashes the data, oopsy, oh well.
how do we know any given lib is not going to just end up introducing bugs into our system? sure, it is an age-old question, but one has to pay more heed to it when looking at such risky-hard features as concurrency or distribution, no? (this goes back to an old thread in clojure where i was asking about how clojure's stm is tested. i personally can't believe that only inspection and no testing is the right way to get things right, but ymmv.) sincerely. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
