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.
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.
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.