Why every dev should avoid 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
Where Should You Deploy In 2026?
Theo - t3․gg
102.6k views
Should we break up AWS over the us-east-1 outage?
Theo - t3․gg
45.8k views
The Future of React
Theo - t3․gg
50.7k views
I ranked every vibe coding app
Theo - t3․gg
75.9k views
React is killing the web
Theo - t3․gg
59.9k views
React 19.2 Dropped Early???
Theo - t3․gg
55.4k views
Which browser should you use right now?
Theo - t3․gg
193.6k views
You should NOT work at a startup
Theo - t3․gg
68.6k views
Every smart AI model wants to kill you (yes really)
Theo - t3․gg
32.0k views
React feels insane
Theo - t3․gg
90.4k views
Top Comments (10)
TL;DR: The "React sucks" article confuses correlation with causation. React isn't the problem; bad data/architecture and weak ownership are. Pick tech you'll actually ship with, get users, then fix performance.
I asked my wife if she preferred applications that use Rust or Python. She just stared at me.
Theos Therapy: Day 1: Do A Day 2: Don't do A Day 3: Why you should reconsider A Day 4: A really suck, It's over.
React is to the front end today like Java was to the back end in the late 90’s and early 2000s. You pick it because it’s the thing you pick, you won’t lose your job for picking it, and you can always find a zillion devs to work your projects.
Every dev picks react because of the ecosystem built around it, because it has tons of libraries.
I don't agree with the article's exact points, but I think React is fundamentally flawed in the sense it has an inverted model of Reactivity. Where every function needs to rerun all over again on every state change(batched), and any object references outside of hooks or even being returned by hooks can create new references and cause a re-render. The new React compiler solves some of these issues, but it's a bandage on top of a problem that shouldn't have existed in the first place IMO. Something like what Vue or Solid do with fine grained reactivity tracking, where only the necessary effects and DOM updates are done would've been much easier to reason about. Even reactive state being tied to components is an unnecessary pattern. That's why you have so many different state management solutions in React, all playing around with contexts and providers. In Vue, you can define reactive state outside of a component and directly consume it in any N components. That's why there's such few state management libraries in Vue, it's essentially a solved problem. But the fact that React grew popular, by intertia meant it got better, because it has the best tooling and community support by far.
Bro never ceases the opportunity to randomly diss flutter
bro really hates rails
"Its not in the performance tab, its in the network tab" facts.
0:44 You're AI guy now.
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: The "React sucks" article confuses correlation with causation. React isn't the problem; bad data/architecture and weak ownership are. Pick tech you'll actually ship with, get users, then fix performance.
I asked my wife if she preferred applications that use Rust or Python. She just stared at me.
Theos Therapy: Day 1: Do A Day 2: Don't do A Day 3: Why you should reconsider A Day 4: A really suck, It's over.
React is to the front end today like Java was to the back end in the late 90’s and early 2000s. You pick it because it’s the thing you pick, you won’t lose your job for picking it, and you can always find a zillion devs to work your projects.
Every dev picks react because of the ecosystem built around it, because it has tons of libraries.
I don't agree with the article's exact points, but I think React is fundamentally flawed in the sense it has an inverted model of Reactivity. Where every function needs to rerun all over again on every state change(batched), and any object references outside of hooks or even being returned by hooks can create new references and cause a re-render. The new React compiler solves some of these issues, but it's a bandage on top of a problem that shouldn't have existed in the first place IMO. Something like what Vue or Solid do with fine grained reactivity tracking, where only the necessary effects and DOM updates are done would've been much easier to reason about. Even reactive state being tied to components is an unnecessary pattern. That's why you have so many different state management solutions in React, all playing around with contexts and providers. In Vue, you can define reactive state outside of a component and directly consume it in any N components. That's why there's such few state management libraries in Vue, it's essentially a solved problem. But the fact that React grew popular, by intertia meant it got better, because it has the best tooling and community support by far.
Bro never ceases the opportunity to randomly diss flutter
bro really hates rails
"Its not in the performance tab, its in the network tab" facts.
0:44 You're AI guy now.