Why Tech Companies Are Moving Off React
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
Your prompts are tech debt.
Theo - t3․gg
31.9k views
A realistic comparison of Opus and Codex
Theo - t3․gg
115.5k views
Theo fell off
Theo - t3․gg
48.5k views
I moved off of Next.js
Theo - t3․gg
142.0k views
You’re all wrong
Theo - t3․gg
76.4k views
Watch this if you hate React Server Components
Theo - t3․gg
45.9k views
The Future of React
Theo - t3․gg
50.7k views
React is killing the web
Theo - t3․gg
59.9k views
React caused an outage for Cloudflare?
Theo - t3․gg
42.0k views
Why every dev should avoid React
Theo - t3․gg
81.2k views
Top Comments (10)
TL;DR: Most of the “React is dead” hype is way overblown. The real problems big companies have with React are usually about app complexity and bad dev practices, not React itself. Hooks, concurrent mode, server components, and the new compiler are all huge wins—especially for large apps. Most “churn” is optional and backward compatible. If your React app is slow or hard to maintain, it’s probably not React’s fault. Don’t jump ship just because of headlines—React is still the best choice for most big projects. Simplicity and good engineering matter way more than the framework you pick!
having 200 devs working on the same app is gonna be hard in any framework 😅
I miss my vue days. Been on the react bandwagon for almost 3 years now after a 3 year hiatus where i only worked with vue. Now i’m doing a lot of mentoring and enablement for other teams/devs and i lost count of how many problems, challenges, performance concerns etc emerge that would be non issues if we were using vue 😢
Clicking on a Theo video because of the cool title not seeing the 1h30m duration is peak YouTube.
Imagine explaining server components, yeah instead of returning json you return html, Full cycle back to php
If AI continues to be a thing then react will never die because all of the frontend UI training data comes from react tutorials
Everybody hates a winner. Seriously though, as much I'd love to jettison React for <shiny-new-framework>, the ecosystem just isn't there and I'm more productive on React and less dependent on one bus factor libs (that more than often are abandoned) as a result. Still, my penchant for shiny objects sends me down the path of giving framework X another try (as recently as a few weeks ago), I'm quickly reminded why React is the right decision for me. Seriously looking forward to when / if Solid gets to critical mass -- until then, liking the changes Reach 19 has brought and plenty of tooling out (that doesn't constantly crash) to help overcome some of React's pitfalls.
As somone who built an app without a framework for fun: I would not do that for a business. It only worked because I had been exposed to ever part of my codebase and had nobody to trip over. Try that with even a 3 person team and be prepared to see 300 different ways of solving the same problem slightly differently. As someone who made an app without a framework for fun, frameworks are what make teamwork the dreamwork
I still use class components for our quite large app, because these functional components just add bloat and boilerplate calls. And no, I have none of the issues you mentioned, because I don't have the habit of making it far more complex than it needs to be.
Which companies?
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
TL;DR: Most of the “React is dead” hype is way overblown. The real problems big companies have with React are usually about app complexity and bad dev practices, not React itself. Hooks, concurrent mode, server components, and the new compiler are all huge wins—especially for large apps. Most “churn” is optional and backward compatible. If your React app is slow or hard to maintain, it’s probably not React’s fault. Don’t jump ship just because of headlines—React is still the best choice for most big projects. Simplicity and good engineering matter way more than the framework you pick!
having 200 devs working on the same app is gonna be hard in any framework 😅
I miss my vue days. Been on the react bandwagon for almost 3 years now after a 3 year hiatus where i only worked with vue. Now i’m doing a lot of mentoring and enablement for other teams/devs and i lost count of how many problems, challenges, performance concerns etc emerge that would be non issues if we were using vue 😢
Clicking on a Theo video because of the cool title not seeing the 1h30m duration is peak YouTube.
Imagine explaining server components, yeah instead of returning json you return html, Full cycle back to php
If AI continues to be a thing then react will never die because all of the frontend UI training data comes from react tutorials
Everybody hates a winner. Seriously though, as much I'd love to jettison React for <shiny-new-framework>, the ecosystem just isn't there and I'm more productive on React and less dependent on one bus factor libs (that more than often are abandoned) as a result. Still, my penchant for shiny objects sends me down the path of giving framework X another try (as recently as a few weeks ago), I'm quickly reminded why React is the right decision for me. Seriously looking forward to when / if Solid gets to critical mass -- until then, liking the changes Reach 19 has brought and plenty of tooling out (that doesn't constantly crash) to help overcome some of React's pitfalls.
As somone who built an app without a framework for fun: I would not do that for a business. It only worked because I had been exposed to ever part of my codebase and had nobody to trip over. Try that with even a 3 person team and be prepared to see 300 different ways of solving the same problem slightly differently. As someone who made an app without a framework for fun, frameworks are what make teamwork the dreamwork
I still use class components for our quite large app, because these functional components just add bloat and boilerplate calls. And no, I have none of the issues you mentioned, because I don't have the habit of making it far more complex than it needs to be.
Which companies?