btw, @alandipert, one disconnect I have with the scenarios described was that Matrix apps, as I code them, work exclusively by event handlers kicking off individual state changes, so the problem dosync solves does not really register for me. The case I had where two related changes were made back-to-back actually turned into four related changes and then at five I broke down and admitted that the five properties should actually be their own "game" object. Then the "restart game" button just needed to change the current-game property to a new game, in one mutation. In a sense, MX exposed a design failure on my part. This reminds me of how

(let [a (f1) 
    . b (f2)]
 (or a b))