thinking-in-react-and-flux
Last updated
Was this helpful?
Last updated
Was this helpful?
Thinking in React
The original guide to breaking a UI into components and setting up data flow
Removing User Interface Complexity, or Why React is Awesome
A long walkthrough that builds up a pseudo-React-like library, demonstrating what React does and why you would want to use it. Has lots of embedded demos.
Describing UI State with Data
Demonstrates modeling the state and actions of an application, and updating the UI based on that.
Common React Mistakes - Unneeded State
Examples of how to think about and model data and UI state
Understanding the Functional Revolution in Front-End Applications
Higher-level tutorial describing functional programming and how it relates to Javascript, UI, and client-side applications
Functional UI and Components as Higher Order Functions
Another tutorial on functional programming and how it relates to React
Components, React, and Flux
A fantastic HTML slideshow that discusses how to organize code as reusable components, and the basic concepts and benefits of a Flux unidirectional architecture
Reactive, Component-Based UIs
Another fantastic HTML slideshow describing the three principles of React: "functional over OOP", "stateless over stateful", "clarity over brevity" (use arrow keys to advance slides)
Why You Should Care About Flux Describes the value in separating "reads" from "writes", and eliminating local state
Lessons Backbone Developers Can Learn From React Discusses 3 lessons from React: "UIs are trees of reusable components", "modern JS is cleaner code", and "don't use DOM for state"
State is an Anti-Pattern Some long-winded but useful thoughts on what makes a good component: "intuitive", "same input -> same output", "pure", and "only side effects are Flux actions"
Why Local Component State is a Trap Thoughts on a "single state tree" vs local component state
Functional Javascript: Reverse-Engineering the Hype A slideshow that talks about why functional-type programming matters, and how it relates to React-type apps.
"Trying to understand why React prefers one-way data binding" Some excellent and very informative discussion on why the "one-way data flow" paradigm is used with React, vs two-way data binding.