React-ing to Rails: Why Ruby on Rails is the best Stop for Web Developer
summary
A nonprofit beneficiary-tracking web app replaces Google Sheets and Access with tablet forms, searchable records, attendance reports and image uploads; initial build with React + MongoDB + React Bootstrap + Chart.js stalls and takes six months without a working MVP, then a Rails rebuild using rails generate scaffold produces a working app and deploys via Sudoku in three weeks vs six months, highlighting faster full-stack scaffolding, built-in features and less tech switching.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:11Client problem and project start
- 7:47Prototyping and user feedback
- 9:37React struggles and Rails discovery
- 12:51Why Rails beats React for this project
- 14:18Seven reasons to choose Rails
- 14:40Acknowledgments and closing
related talks
31mReact.js on Rails
31mReact on Rails
07mBuilding Real-Time App with React/Redux/Rails/RethinkDB
36mFront-End Sadness to Happiness: The React on Rails Story
25m"React integration into existing Rails applications"
39mBuilding a highly scalable exchange - To react or not to react
28mBack to React: The Story of Two Apps
35mUsing GraphQL and Relay for hybrid RoR apps