> you can always read the signal at the top and pass their values to an external function Which is basically re-inventing a dependency array... except it's not

> you can always read the signal at the top and pass their values to an external function Which is basically re-inventing a dependency array... except it's not explicit and now I have to look at another function as well. I don't understand how you are supposed to reason about complex effects with the signals model. > Random example Why would I want to complicate things with conditional effects though? It makes it so much harder to debug and reason about. > the entire array will be diffed each time, whenever any of them change your effect will be re-executed, even if something you don't care about in that moment changed An array diff on the order of ~10 elements isn't an expensive operation and I can implement conditional logic in React just like you've demonstrated here. What is different about signals in regards to conditional flows? > if you don't want to call a hook you can just not call it. If you want to nest effects you can do that I'm not convinced this is desirable. Complex implicit reactive effects seem fragile and difficult to debug and reason about. This is somewhat mitigated with React because of the Rules of Hooks, which gives you expectations about how your code/system should behave but even then people have complained about them being difficult to understand. This feels like a step backwards in terms of complexity. Without better tooling/observability (E.g. easily trackable effect history, value history, etc that is integrated into the dev env) implicit reactive dataflow based systems feel like they will be way harder to manage.