Navigate Select ESC Close

Why every dev should avoid React

2025-08-23 Science & Technology
81.2k
2.6k
465
Theo - t3․gg
Theo - t3․gg
539.0k subscribers

Unlock all features

FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.

Description

I always love breaking down these "react sucks" articles. There is some genuine good in here, but oh boy is it also so so wrong... Thank you Augment Code for sponsoring! Check them out at: https://soydev.link/augment SOURCES https://medium.com/@fourtyeighthours/tech-founder-entrepreneur-this-is-why-you-should-avoid-react-js-in-your-app-41fe9fb7511b https://www.youtube.com/watch?v=Cifkb-ZVps4&t=10s Want to sponsor a video? Learn more here: https://soydev.link/sponsor-me Check out my Twitch, Twitter, Discord more at https://t3.gg S/O Ph4se0n3 for the awesome edit 🙏

Top Comments (10)

@sierragutenberg 2025-08-23

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.

625 13 replies
@wadecrawford8494 2025-08-23

I asked my wife if she preferred applications that use Rust or Python. She just stared at me.

319 12 replies
@wilsonibekason 2025-08-23

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.

254 8 replies
@Talk378 2025-08-23

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.

235 11 replies
@sohambhattacharjee8314 2025-08-23

Every dev picks react because of the ecosystem built around it, because it has tons of libraries.

72 3 replies
@itskishank 2025-08-23

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.

57 12 replies
@CrustyHoot 2025-08-24

Bro never ceases the opportunity to randomly diss flutter

41
@pete-dy 2025-08-23

bro really hates rails

34 2 replies
@josephvictory9536 2025-08-23

"Its not in the performance tab, its in the network tab" facts.

28
@KenKovacs 2025-08-24

0:44 You're AI guy now.

12

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

App screenshot