I am a big fan of Signals. It’s the best state-management concept I've come across (also my team-mates). We even use it outside of the frontend space, e.g. in long running instances / services or complicated numpy calculations.
One of the core characteristics why it's so easy to reason about, is that the reactivity is indeed synchronous. We know most of the time, what every signal set() does when we constraint ourselves Effects not allowing to set other Signals.
Integrating async as first class citizen into the core is indeed interesting. I wonder how it impacts the ergonomics and state reasoning in the end.
Integrating async as first class citizen into the core is indeed interesting. I wonder how it impacts the ergonomics and state reasoning in the end.
Need to test it out.