TL;DR: there is no one silver bullet for the UI in general. As a rule practical and manageable UIs use all these approaches at the same time. Components, clas

TL;DR: there is no one silver bullet for the UI in general. As a rule practical and manageable UIs use all these approaches at the same time. Components, class based and/or functional (fe: UserSection, InventoryTable ), are in principle loosely coupled. They may not know about each other and use messages to communicate. The Flight by Twitter ( https://flightjs.github.io/ https://flightjs.github.io/ ) was/is probably the first practical thing that pioneered that approach. The Flight is not even a framework but rather a design principle. In fact it is an anti-framework - it postulates that in practice each component may have its own optimal internal architecture. One component is better to use React-ivity, another - Angular-ish data binding, etc. On some, immediate mode drawing is the most natural. Smaller the task (component) - greater the chance to find silver bullet for it.