136: Michael Chan - React Is Not a Rails Competitor
Episode
68 min
Read time
2 min
Topics
Productivity, Leadership, Design & UX
AI-Generated Summary
Key Takeaways
- ✓Framework Completeness Gap: Create React App generates front-end applications with no data persistence or service connections, requiring developers to separately implement authentication, database access, email sending, and background job processing that Rails provides out-of-the-box through integrated conventions.
- ✓Role Specialization Trade-offs: Developers entering tech as front-end specialists often lack full-stack product thinking, creating communication friction between teams and missing the satisfaction of building complete applications from database to user interface that earlier generations experienced with frameworks like Rails.
- ✓Next.js API Routes Evolution: Next.js introduces serverless API routes as first-class features, enabling privileged server-side code execution for tasks like Stripe refunds within React projects, though currently lacking the opinionated conventions and security patterns that make Rails productive for complete application development.
- ✓CSS Custom Properties Revolution: CSS variables enable composition within single properties, allowing developers to set box-shadow colors once while maintaining complex multi-shadow effects, and create utility classes that only modify variables rather than duplicating entire CSS rules, dramatically reducing stylesheet size.
- ✓Authentication Architecture Reality: HTTP-only cookies remain the recommended authentication approach even for single-page applications according to framework creators like Guillermo Rauch, contradicting the common assumption that React apps should use JWT tokens in local storage for session management.
What It Covers
Michael Chan explains why React handles only front-end rendering while Rails provides complete application infrastructure including database connections, authentication, and background jobs—addressing the misconception that React replaces full-stack frameworks like Rails.
Key Questions Answered
- •Framework Completeness Gap: Create React App generates front-end applications with no data persistence or service connections, requiring developers to separately implement authentication, database access, email sending, and background job processing that Rails provides out-of-the-box through integrated conventions.
- •Role Specialization Trade-offs: Developers entering tech as front-end specialists often lack full-stack product thinking, creating communication friction between teams and missing the satisfaction of building complete applications from database to user interface that earlier generations experienced with frameworks like Rails.
- •Next.js API Routes Evolution: Next.js introduces serverless API routes as first-class features, enabling privileged server-side code execution for tasks like Stripe refunds within React projects, though currently lacking the opinionated conventions and security patterns that make Rails productive for complete application development.
- •CSS Custom Properties Revolution: CSS variables enable composition within single properties, allowing developers to set box-shadow colors once while maintaining complex multi-shadow effects, and create utility classes that only modify variables rather than duplicating entire CSS rules, dramatically reducing stylesheet size.
- •Authentication Architecture Reality: HTTP-only cookies remain the recommended authentication approach even for single-page applications according to framework creators like Guillermo Rauch, contradicting the common assumption that React apps should use JWT tokens in local storage for session management.
Notable Moment
Chan reveals Planning Center operates eight separate Rails applications serving as API backends, each with varying amounts of React on top—some routes render full React apps while others mount single complex forms, demonstrating that production React development still depends heavily on traditional server frameworks.
Episode Transcript
In this episode of Fullstack Radio, I talked to Michael Chan about why React is not a Rails competitor and why we're all still gonna be building bespoke back ends for years to come. This is Fullstack Radio episode one thirty six. So okay. The reason I wanted to have you on the show a while ago I don't have the date on this because I only have a screenshot and I'm too lazy to find the real tweet. You tweeted, so many developers will never experience the unadulterated bliss of running rails new. No other framework gives you as much useful structure and tooling out of the box. And I saw this tweet and I thought, I'm glad that I'm seeing someone from, like, the front end space kind of say this because I feel like there's this, like, gap that I haven't been able to cross, which is, like, how are all these people who identify as, like, React developers, like, building real stuff and putting it on the Internet if they're not still also using tools that let them talk to a freaking database? You know what I mean? Yeah. So I think a best place to start maybe would just be to learn a little bit more about, like, your kind of journey as a developer because it's I've been looking forever to find someone who I felt, like, knew the the rails world back in the day and is super tightly integrated into the, React ecosystem today. So, like, how did you get started? What sort of stuff do you have experience with? What's your story? Yeah. So I started I think one of the first technical books that I bought was, was something to do with Rails or, like, I don't know, one of the early Rails books and then also an early Ruby book. Yep. I think it was right around the time that, DHH had made that talk and he was, like, showing you how to build a blog in fifteen minutes. And I was, like, oh my gosh. Like, I don't know anything about programming, but, like, that capability looks like something that I want to invest into personally. Got it. Unfortunately, like, Rails really does require, some previous programming knowledge. It's not a beginner friendly framework. And I think I've learned, like, since then that it's, it gives you a lot of tools if you're a capable developer already. But it's not really like a, hey, like, this is this is a great first introduction into programming. It's not it's not that at all. If you don't have the the the pain points and, like, the problems, then you don't really appreciate the solutions that that Rails has given you. And so, I I mean, I couldn't I couldn't do it. I couldn't hack it. And a friend mine was like, hey, just like like, forget all that framework stuff. Just, like, learn PHP and, like, throw up a couple …
Get the full transcript (13,133 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 65-minute episode.
Get Full Stack Radio summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from Full Stack Radio
153: DHH – Omarchy and Designing Your Own OS on Arch Linux
Aug 21 · 76 min
The Art of Manliness
Born to Carry — How to Build Strength, Stamina, and Sanity Through Rucking
Feb 24
More from Full Stack Radio
152: Ben Orenstein - How to Stand Out When Applying for a Job at a Small Company
Jan 28 · 47 min
ZOE Science & Nutrition
Recap: How exercise slows brain ageing | Dr Wendy Suzuki
Feb 17
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links.
Tools
“Create React App generates front-end applications with no data persistence or service connections, requiring developers to separately implement authentication, database access, email sending, and background job processing that Rails provides out-of-the-box through integrated conventions.”
“Next.js introduces serverless API routes as first-class features, enabling privileged server-side code execution for tasks like Stripe refunds within React projects.”
“Planning Center operates eight separate Rails applications serving as API backends, each with varying amounts of React on top—some routes render full React apps while others mount single complex forms, demonstrating that production React development still depends heavily on traditional server frameworks.”
“Next.js introduces serverless API routes as first-class features, enabling privileged server-side code execution for tasks like Stripe refunds within React projects, though currently lacking the opinionated conventions and security patterns that make Rails productive for complete application development.”
More from Full Stack Radio
We summarize every new episode. Want them in your inbox?
153: DHH – Omarchy and Designing Your Own OS on Arch Linux
152: Ben Orenstein - How to Stand Out When Applying for a Job at a Small Company
151: DHH – Building HEY with Hotwire
150: Secret Screencasting Tips & Behind the Scenes of Tailwind CSS 2.0
149: Choosing a Payment Processor, Radical Icons & W3C Hype
Similar Episodes
Related episodes from other podcasts
The Art of Manliness
Feb 24
Born to Carry — How to Build Strength, Stamina, and Sanity Through Rucking
ZOE Science & Nutrition
Feb 17
Recap: How exercise slows brain ageing | Dr Wendy Suzuki
Huberman Lab
May 7
Essentials: Compulsive Behaviors & Deep Brain Stimulation | Dr. Casey Halpern
Ologies
Mar 18
Allergology (ALLERGIES) with Zachary Rubin
Decoder
Feb 23
Hank Green lets loose on YouTube, billionaires, and algorithms
Explore Related Topics
This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.
You're clearly into Full Stack Radio.
Every Monday, we deliver AI summaries of the latest episodes from Full Stack Radio and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime