> Over all it suited my needs and worked out well. It could probably have been > designed without needing this but I liked being able to keep different > capabilities independent of each other (and not worry that maybe a different > capability registered a handler for the same events).
I'm glad to hear it worked out well for you. I am currently working with a large redux application where we had to use sagas to coordinate independent components. The sagas work wonderfully (generators and yields, like core.async, are great mental models), but it does break a lot of the debugging tools because you have now given up 100% "pure 1-to-1 this happened then that happened". Generators/sagas/core.async hold onto state internally, so it's a pretty big sacrifice to give up wholly serializable state. -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/clojurescript.
