DEV Community

Cover image for A Tribute to React

A Tribute to React

Alexey Antipov on January 29, 2024

Attention: This article may cause discomfort, particularly for individuals not from the React community. No offense is intended. Proceed at your ow...
Collapse
 
patfinder profile image
Le Vuong • Edited

Software need principles, and its shown in React. And as it usually says, there is no silver bullet. Developers need to learn how to build, and evolve their system, combine the tools together. React only do one thing and it do it best. That is the reason for its success.

Collapse
 
eltupac profile image
Nehuen Covelo

Completely true, and to add some more: Whenever you enter a video/blog that says "React is bullsh*t/React is useless" is people that doesn't understand the approach or the flow behind scenes and just limitates to add community hate to the strongest frontend ecosystem that dominated over the last years.

Collapse
 
ninjin profile image
Jin

Has the react community already played enough with state managers or do they continue to change them every year?

Collapse
 
aantipov profile image
Alexey Antipov

That's a question to React Community :)

Collapse
 
ninjin profile image
Jin

You simply shift the problem of the framework onto the heads of its users.

Thread Thread
 
patfinder profile image
Le Vuong

In this post heading image, there is a text say "Not a framework", that might be the reason i guess :) .

Thread Thread
 
ninjin profile image
Jin

Don't find it very risky to choose a “non-framework” as the basis of the application architecture?

Thread Thread
 
aantipov profile image
Alexey Antipov • Edited

There are tradeoffs everywhere.
You can try build everything and fell short delivering it.
Or you limit the scope of your efforts, excel at it and let others fill the gaps.
React chose the latter and that led them to where they are.

Don't see a reason to be angry at React because of it

Thread Thread
 
patfinder profile image
Le Vuong

Properly not, as the React success said. Anyways, many find it more comfortable building system based on popular and well supported framework. Its developers' choice and responsibility.

Thread Thread
 
ninjin profile image
Jin

The funny thing here is that somehow I single-handedly did what a huge corporation could not: my own reactive builder, hundreds of libraries, the coolest reactivity system, an isomorphic web-framework, hundreds of widgets, a decentralized database, dozens of applications, and even.. in between, I managed to fix the React.)

Thread Thread
 
aantipov profile image
Alexey Antipov

That's funny

 
Sloan, the sloth mascot
Comment deleted
Collapse
 
jwhenry3 profile image
Justin Henry • Edited

I definitely agree with the sentiments of this article. One area I really wish they would consider is the reactivity aspect, as they should bring signals (officially) into react so we can unify state management across Angular, Solid, React, etc. Signals are so powerful and lightweight, I am surprised why it hasn't become the standard.

Collapse
 
aantipov profile image
Alexey Antipov • Edited

the "Reactivity aspect" is not a free lunch. It comes with its own tradeoffs.

It's not something unambiguously better. This is where I completely understand the apprehension of the React team and them being cautious.

Implementing something just because other implement it - also not a strong point.

I myself was excited about reactivity API in Vue and Solid for some time. But having built apps with it, I stopped being excited about it.

Collapse
 
efpage profile image
Eckehard

Image description

Collapse
 
roy_weru profile image
Roy Weru

Next JS a framework on top of React JS just takes things on another level