Glitches fixed in RxJS?

[dakom]

From a rough test using the code from the book, it seems glitches are fixed in RxJS v5.

Can someone confirm or explain in more detail how RxJS v5 continues to differ from Sodium?

Here's a codepen, just switch the libraries in the html to see the difference

[Ziriax]

No, it just seems the behavior of range has changed somehow (maybe a different default scheduler).

Also, in a real FRP system, your example code should output

101
202

but your RxJS 5 version outputs

102
202

So the concept of 'latest' is still weird in RxJS 5.

Here's a fork that shows that glitches still occur:

The code should always print 1000*x + x, but it also prints the glitches

[dakom]

hah, I hadn't even noticed that the result was 102 instead of 101... I just saw 2 results instead of 3

good catch, thanks!

[Ziriax]

You can prevent glitches rather easily in RX, you just need to sample the combineLatest node in the correct order, see for example:

Note that technically speaking this still produces glitches, but the sample operator throws these away.

However, the computational overhead of this RxJS solution could be a lot less than a full blown breath-first glitch-free dataflow system like Sodium.