They aren&#x27;t a problem if the operations at the leaves of the graph are idempotent, which is usually the case if these operations are UI repaints.<p>If the operations are for other effects - such as Ajax calls - then glitch elimination is handy.  Eliminating glitches at the dataflow level prevents debounce logic from leaking out to the code performing the effects, preserving the clarity and generality of that code.<p>I find glitch elimination most useful when the dataflow graph is value-propagated, vs. event-propagated, as it is in the dataflow library I helped implement, Javelin - <a href="https:&#x2F;&#x2F;github.com&#x2F;hoplon&#x2F;javelin&#x2F;" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;hoplon&#x2F;javelin&#x2F;</a><p>Javelin also supports transactional input, another feature that&#x27;s  helpful when building dataflow graphs on which effects other than UI-repaint are hung.