All the terrible things I did the first time I made a complex React app
summary
Built a Gmail-like messaging system in six weeks with a Rails backend and a React front end mostly solo, and it mostly breaks: manipulated the DOM with jQuery, creates huge tangled components, and wires ad hoc bidirectional state so bugs multiply. The app is rendered via react-rails gem that drops the entire React app into one Rails view with no react-router. Later fixes: move to unidirectional state with redux, split components, or run Rails as an API and a separate React app.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:03Kindness and consideration
- 1:52My task
- 2:20My background
- 4:49What would I need
- 5:51The learning process
- 7:19Manipulation of the DOM
- 8:22Javascript
- 9:56Declarative Style
- 11:20A Few Issues
- 11:50My Other Option
- 12:09Back to React
- 13:02Components
- 14:13Flux
- 16:04Data Flow State
- 16:54Component Management
- 17:35Learning React
- 19:35React Rails Gem
- 20:42Separating React and Rails
- 21:38Choosing React
- 23:03The good things
- 25:03Conclusion
- 25:58My advice
related talks
28mBack to React: The Story of Two Apps
31mReact on Rails
40mHow I learned to love React
07mBuilding Real-Time App with React/Redux/Rails/RethinkDB
31mReact.js on Rails
18mReact-ing to Rails: Why Ruby on Rails is the best Stop for Web Developer
36mFront-End Sadness to Happiness: The React on Rails Story
37mReact is hard but not why you may think