4 ms·

React without flux/redux/whatever and state distributed though the component tree instead is a thing. It's not the right solution for every problem, anything l

React without flux/redux/whatever and state distributed though the component tree instead is a thing. It's not the right solution for every problem, anything like, but with a bit of thought about where it makes sense to keep the state, it can work pretty well and components which know how to fetch their own data can sometimes be easier to reuse in other contexts than, e.g., components from a full-on redux application. See also, Relay (or om.next) with "co-located queries" for a declarative take on this.

e12e 9y ago
I'm not sure how you'd write an application without a data model? If you take a look at the first figure here: http://heim.ifi.uio.no/~trygver/themes/mvc/mvc-index.html http://heim.ifi.uio.no/~trygver/themes/mvc/mvc-index.html it's hard to see how react/flux isn't just dealing with the controller/view bit - perhaps in a better way - but it's still a bridge between the users mental model and the computers data model? And it's likely that the data model is at least somewhat complex, if it involves some kind of MVCC/ACID/transactions and/or data normalization?