[ffsm8]

Debouncing correctly is still super hard, even with rxjs.

There are always countless edge cases that behave incorrectly - it might not be important and can be ignored, but while the general idea of debouncing sounds easy - and adding it to an rxjs observable is indeed straightforward...

Actually getting the desired behavior done via rxjs gets complicated super fast if you're required to be correct/spec compliant

[pas]

can you recommend some reading about the topic? also maybe point to some specs that require (and describe?) fully correct debouncing? thanks!

[ffsm8]

Not really, but I feel like you might've misunderstood me.

The debouncing of rxjs just takes an observation and debounces, which is essentially throttle with inverted output (it outputs last instead of first).

That's almost never what the product owner actually wants, at least IME.

If they give you any kind of soec, you'll quickly realize that limit.

I.e. debouncing after the request happened is impossible, just like cleanly abortion requests on exit or similar.

There are also often a ton of signals you need to add to the observale for all the events the PO wants to respond to, such as opening dialogues, interacting with elements outside of the context of the debounces event chain etc pp

It just keeps getting more complicated with every additional thing they come up with. But if they're fine with just living with the technical limitations, all is fine.