Rethinking the View using React.js
summary
React.js replaces templates with composable components, JSX as a preprocessor, and one‑way props plus local state to describe UI; the runtime uses a virtual DOM diff so updates stay fast. Integration uses the react-rails gem which precompiles .js.jsx, mounts components into ERB, supports server‑side rendering (but lacks document access and requires global dependencies), and an example implements a tweet timeline that polls every 5 seconds and re-renders successfully.
AI-written summary · about
chapters (30)
- 0:00Intro
- 0:42BIGBinary
- 2:17Simple
- 3:34Unconventional ideas
- 5:00Component is fn()
- 5:48Reusable
- 6:18Composable
- 6:38Separation of concerns
- 10:46No templates
- 12:37Managing Data
- 13:07Data changing over time is root of evil Pete Hunt
- 14:13One way data flow
- 14:31Immutable
- 15:54State is internal
- 17:17props state
- 17:37Responding to state changes
- 18:35Refresh
- 19:20REDDOT Re-Rendering the component tree
- 19:45Virtual DOM
- 20:38Minimal set of changes
- 20:51Batch updates
- 21:01Nothing is new!
- 21:57gem "react-rails"
- 24:54Syncs with asset pipeline
- 25:16Server side rendering
- 26:04Component Generator
- 26:27React Native
- 27:06Learning Curvel
- 27:40REDZOT Easy to sneak into existing projects
- 27:51experience!
related talks
31mReact.js on Rails
21mIntroducing React View: A Set of Tools that Closes the Gap between Users, Developers
34mI Heard React Was Good
30mReact: Rethinking best practices
01h 04mWhat makes React different?
41mReact - Rethinking Best Practices (updated)
36mReact: RESTful UI Rendering
27mReact: Learn Once Write Anywhere