4 ms·
That's because you used React alone, which works as a top-down view engine. If you want to modify something in the view, you have to go back to the top and modi
by rakoo 12y ago
That's because you used React alone, which works as a top-down view engine. If you want to modify something in the view, you have to go back to the top and modify the model. Instead of doing it manually, Facebook has created the Flux architecture to help you scale this process efficiently.
- marknutter 12y agoSo Facebook created an architecture to solve a problem their new web framework introduced?
- neftaly 12y agoNo, they created an architecture and decoupled their web framework from it.
- findjashua 12y agoWhich was a poor decision, imho. Using React only makes sense with Flux, why separate them? Furthermore, the examples on React's docs use the pass-down-the-event-handlers madness, instead of using Flux. React+Flux is a good solution, but the documentation leaves a lot to be desired.
- nutate 12y agoReact components can be brought into any architecture. Using them with flux certainly simplifies many things, but by the same token, flux apps can be written using other libraries (react based like om, or even full frameworks like angular). The decoupling is good. It lets you try out a component from http://react.rocks/ http://react.rocks/ without diving into a fully architectured SPA.