On Tue, Mar 17, 2015 at 5:47 PM, James Gatannah <james.gatan...@gmail.com> wrote:
> FWIW, we've been using something that smells an awful lot like nested > systems for months now. I never realized we weren't supposed to. > It's not that nested systems *never* work, but from what I've seen they cause more complications than they're worth. The 'component' model doesn't forbid it, but it does not support dependencies between components in different "subsystems." I've found it easier to keep system maps "flat" and use namespaced keywords to distinguish "subsystem" groups, even in large systems with 30+ components. –S -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
