3 ms·
It has a fine explanation of the pattern: http://facebook.github.io/react/docs/flux-overview.html http://facebook.github.io/react/docs/flux-overview.html but wh
by neves 12y ago
It has a fine explanation of the pattern: http://facebook.github.io/react/docs/flux-overview.html http://facebook.github.io/react/docs/flux-overview.html
but what isthe reasoning in using this architecture? Or in pattern speak, what are the forces that this pattern is considering? I can't find a clear explanation about which problems is it trying to solve.
- tracker1 12y agoIn larger web based applications, tracking down side effects becomes increasingly difficult with patterns that implement two-way data binding (observables) or ad-hoc injection. This also in part takes into account part of why React renders the way it does. With the flux pattern(s) along with React's rendering pipelines, you can have heavy data flows, with minimal side effects and a slightly easier time in terms of tracing the flow of data.
- kaonashi 12y agoEncouraging composition and simplifying event flow.