Sun Jun 18 23:59:21 EDT 2017

Flux, tree-diff

If I understand properly, the point of flux is to re-render everything
after a user event.  There is a single direction of data flow which
terminates in the update of the user's display.

The main benefit: it allows the view implementation to be functionally
dependent on the view specification.  No fussing around with state
that we didn't know where it came from.

React just re-renders in an efficient way.  But what if we don't
really need to do that.  What if our specification -> implementation
function is simple enough?