It's intriguing to see that almost every JavaScript client framework has now implemented signals.
A pattern that was once deemed old and primitive...
For further actions, you may consider blocking this person and/or reporting abuse
It would be about time we move to new paradigms, the current state management is stagnant and we, the developers, shouldn't be the ones optimizing for memoization in our components.
Why not?
HTMx is the answer to this question
How is HTMX the answer? merely a fancy html injection parser written in plain old Javascript.
Lol, yea... No 😂
You are absolutely right, but sadly it seems that the React Team is so biased towards specific patterns that they completely ignore the opinions of the developers using their product.
Signals is such an old concept. People go nuts over something so trivial.
Well...
Server-side rendering is also a pretty old concept, yet the industry is falling head over heels for it.
But seriously, back when signals were popular, we weren't building these huge single-page applications.
But now a large movement of developers found that signals can drastically increase the performance of their applications, hence the renewed popularity.
I think the reason why react are not adopting signal, is because they want to give developers full power and responsibility of the way there application behave.
Maybe so, but it does come at the cost of performance and causes tons of spaghetti code in the process.
And a lot of bugs.
They may also be scared of taking drastic decisions at this point, React's adoption is massive and an improper execution could alienate the community.
Everything they're releasing, from concurrency to new hooks, is meticolously planned to avoid breaking changes and offer a seamless dx during the transition.
What you said is true. But most of developers that try signal appreciates it and love it, and even want to continue using it.