need to check state too in shouldComponentUpdate
typo
make the api consistent
give the owning node access to state and path
dom/set-state! needs to invalidate the path to the component
don't use setState, triggers re-render just set state directly
remove bad ideas caused by bug introduced by set-state! updating the path.
need to check that a key was specified
a version of update! that takes 2 params
fix api so we can update the app directly
replace! is conceptually problematic
better naming, om basically gives you a cursor in a tree
reorg