React once dazzled the web development world with its promise of a clean, component-based approach. Fast-forward to 2025, and the once-revered fram...
For further actions, you may consider blocking this person and/or reporting abuse
I have been preaching this for over a year. I'm a Svelter. In my eyes, Svelte and SolidJS are the ones to to climb to the top. Vue? Not so much. Its syntax is inferior, IMHO. Svelte for JSX haters, SolidJS for JSX lovers. That will be it in 5 years.
If we are keeping all options on the table, I would also include LiveView into the mix of alternatives.
As long as it’s signal based and not react, it’s fine with me
Awesome artictle, I am a Vue developer and I sometimes wonder to learn React because of amount job offers but I see that it's not as pretty as it looks.
And you base this opinion on someone's opinion who clearly hates React? I guess it's normal these days to base everything on subjectivity ☹️
Hmm, I don’t hate react. Hate is a very strong word . I use react professionally on daily bases. I think there are some obvious issues with it, especially compared to modern and more developer friendly solutions.
If it was just several of these or if it was just my issues I would’ve probably just ignored them, but based on my experience working with 100s of other devs, these are common pitfalls and unnecessary constraints.
Nothing is ever perfect, but most of these issues could easily be resolved by introducing signals. And I believe the majority of the react community would agree, if they ever get the chance to try them.
Also if you don’t think these issues make sense how would you explain the 3-4 years of efforts in writing the react compiler? The funnies part is they renamed it to compiler with the hope we will forget about the forget part. How could anyone justify such a monumental failure? Even the react team admitted that some of the fundamentals are mistake and a bunch of them left…
I agree React compiler is a big mistake and signals are great and probably the future, but I disagree that switching to something that uses signals will solve all the pitfalls that React has. The pitfalls are inherent to a framework without batteries included and a big part of the community prefers that freedom, which is why React became popular in the first place and why it has such a big ecosystem.
This is the article I am waiting. Thanks for the great article requiring a real&high expertise!
So what is a better option? I mean, you have a good argument but give no options for a replacement, even for the short-term.
The article mentions signals. Any signal based framework should do. If you need more specific recommendation I would go with Vue (also mentioned in the article). The point of the article is to summarize how bad react is compared to literally anything else.
Interesting article.
Point 5 seems unrelated/orthogonal to most of arguments.
i tested qwik and well it seem to be growing well