> I stated this very clearly, saying "complex implicit reactive effects seem fragile and difficult to debug and reason about".
It is definitely easier to reason about dataflow in a good incremental library with dependency autotracking ("Self-Adjusting Computation"[1]) than to reason about nondeterministic concurrent rendering in React :)
If you're building something that is heavily focused on computing values rather than more event driven effects I could see a reactive system being more useful and appropriate though.
I'd love to hear from developers/teams who have built complex systems with a reactive framework (Solid, Signals, etc) to hear about the upsides and downsides of doing so.