Clojurians Log v2

Since 0.12, the async rendering queue was removed because of all sorts of subtle bugs, so this pipeline is simpler, but has this side effect. I've worked around it now by doing a local atom to global atom debounce on all input and text area fields.

You probably need some form of debounce on every part of your app that rapid-fire updates your global atom

I had another thought, but it escaped.. xD

Oh yes. This happens because watches on atoms fire off in the swap process. If that could be setup to debounce after swap, this could mitigate the issue.. though debouncing times are quite situational, so you'd want to be able to configure for your use case

No unfortunately not, don't have time atm

hmm why would rendering and input changes be sychronized?

To quote from your admirable conclusion, "It seems that Rum 0.12.3 regressed in terms of asynchronous rendering, insisting on fully finishing up rendering update before processing the next key event." ... great catch and where would this occur in the rum code? (thinks to self)