I use React a lot, as well as hooks (though, generally, I find that many hooks aren't even necessary w/ a bit of refactoring of the app logic).
With that in mind, I wonder how difficult it will be for them to add signal support into the library.
It feels like maybe React will be replaced, more often, if they can't keep up w/ the rest of the libraries that use signals.
It seems like a hacky "signals" concept could be made to work with React, by using an event emitter and a custom component (or hook) that accepts a signal as a property ("true" signals support is totally different, I know), though it wouldn't be nearly as optimal as signal support in the library itself.
I'm not really sure where React's priorities are now. It seems they are targeting more and more SSG than true frontend, these days, while I actually enjoy making SPA's as I usually make media-type applications that I want to keep some sort of streaming persistence active as I navigate (that kind of thing intrigues me as well).
They say they want to make a "compiler" and I assume the fundamental reason for that is because of some realization that hooks w/ dependency arrays seems a bit archaic compared to the other libraries that don't even need them.
With that in mind, I wonder how difficult it will be for them to add signal support into the library.
It feels like maybe React will be replaced, more often, if they can't keep up w/ the rest of the libraries that use signals.
It seems like a hacky "signals" concept could be made to work with React, by using an event emitter and a custom component (or hook) that accepts a signal as a property ("true" signals support is totally different, I know), though it wouldn't be nearly as optimal as signal support in the library itself.
I'm not really sure where React's priorities are now. It seems they are targeting more and more SSG than true frontend, these days, while I actually enjoy making SPA's as I usually make media-type applications that I want to keep some sort of streaming persistence active as I navigate (that kind of thing intrigues me as well).
They say they want to make a "compiler" and I assume the fundamental reason for that is because of some realization that hooks w/ dependency arrays seems a bit archaic compared to the other libraries that don't even need them.