@malcolmsparks: There are large parallels between a component-ized (as in the start/stop protocols) complex server app and an Om.Next/React style UI. (Non UI)Components don’t promote reusability unless there’s something like what Om.Next presents. I realize now that is sort of what I was trying to do with Aero, albeit poorly. (Translate between graph/tree). I do think your simplifications are ultimately going to pay off in the long run.
I’ll keep this kicking around the back of my brain, I think there might be some wins here (not necessarily with aero) regarding systems that heavily embrace component.