> If this convention can be used in React, what is the "no-framework framework"? What's the point? I think the point is a "no-state handling framework". It see

> If this convention can be used in React, what is the "no-framework framework"? What's the point? I think the point is a "no-state handling framework". It seems like you can combine this with something like morphdom to get React-like merging for pure DOM updates, and the state-handling is via this hierarchical approach. Or your DOM construction can be via a vDOM library which then handles the merges for you.