I have to agree that it's a difficult read, and I'm someone who has done a fair share of looking at these different architectures. But the broad-strokes recomm

I have to agree that it's a difficult read, and I'm someone who has done a fair share of looking at these different architectures. But the broad-strokes recommendations seem approximately like these things I would say(which are not exactly the things the author says): * Some things are best done in an incremental fashion rather than a big "update" * You often need to copy state in your UI code * It helps to focus on building explicit synchronization points(which I turn to FSMs to do) * Modelling abstract cursors on data is a helpful UI idiom