[petilon]

Sorry none of this makes any sense to me. You can't have cyclical data binding when you only have 1-way data binding. MVC is absolutely perfect for stateful use cases. In fact, it is React that suffers a total breakdown in stateful use cases. If your component is stateful and you need to update props then the recommendation is to set and change a key, which replaces the component with a new instance. This of course eliminates any benefit that React provides.

[yazaddaruvala]

I'll try one last time:

> Sorry none of this makes any sense to me.

If you're not familiar with the MVC variants (MVVM, MVP, MVI, MOVE)[0][1] we should start there.

Next you should read through some common mistakes of Backbone.js like applications https://www.toptal.com/backbone-js/top-8-common-backbone-js-... and some criticisms of MVC on HackerNews in 2012[0].

Finally if you haven't before these talks, they are the ones that sold me on React:

- https://www.youtube.com/watch?v=-DX3vJiqxm4

- https://www.youtube.com/watch?v=DgVS-zXgMTk

- https://www.youtube.com/watch?v=nYkdrAPrdcw&t=203s

[0] https://medium.com/@pinarkocak/mvc-mvp-and-mvvm-design-patte...

[1] https://news.ycombinator.com/item?id=4189811

[petilon]

Sorry your last attempt failed. If you have been following React discussions on HN you know there's massive criticism about hooks. MVC is still the predominant pattern and for very good reason. Backbone.js is not relevant for this discussion.