> Arbitrary side-effects coupled with asynchronicity are a recipe for Heisenbugs.

I find it easy to avoid side-effects in imperative reactive code. With side-effects I wouldn't call it reactive.

> , if you add in the constraint that you can't change signal routing at runtime

Once again, this is easy in imperative code.

I am not complaining about functional code. It definitely has its place (just not for me). I just finished an awesome product with imperative reactive code and I thought maybe I was missing something.