Writing a &#x27;driver&#x27; to integrate my low level UI component library to be usable with React.  My major issue was the &#x27;rule&#x27; that a parent can&#x27;t access the &#x27;state&#x27; of it&#x27;s children; this turned a 2 hour job into a 3 day job for me just trying to find a way to get access to this state through all of the lifecycle callbacks while instantiating children at the same time.<p>When asked in #reactjs, they said that if you need access to a child&#x27;s state you should put it into the parent, which makes sense but not in my case.  There is a natural way of hiding working &#x27;upwards&#x27; through the chain, but I can&#x27;t say I&#x27;ve seen it ever work downwards like in React, and I found that rather frustrating and difficult to work around.