Fwiw I did work on a "reactive" Karax with reactive variables and sequences and a dependency graph. It's a bad abstraction because when the examples get more complex than "todo app" it encourages infinite updates. Component A changes that triggers automatic changes to component B which refers back to component A so it triggers changes and so on.
Good abstractions don't introduce entirely new bug categories...
