EDIT: The article is about javascript. Everything below does not apply to javascript. You need more than one thread, at least, for any of these problems.<p>I strongly suspect that combining async streams will prove to be a problem in practice, whether we resolve glitches or not. This article requires quite subtle reasoning about async systems. In my experience this type of reasoning is rarely done effectively on real life projects.<p>I am not criticising Rx, I am interested in Rx. But I am always concerned when a project&#x2F;community starts producing articles on very subtle topics and claims &#x27;x isn&#x27;t a problem if you just understand it properly&#x27;. Here properly probably means deeply, and deep knowledge in software is scarce. There are too many things to know, to know many things deeply.<p>Let me look at one example (and please comment if I&#x27;m really not understanding something).<p>So we consume, asynchronously, two streams. Because they are asynchronous we might hit some point where it&#x27;s a bit uncertain where two outputs are related.<p><pre><code>    errors            ---e1----e2------------------
    userActions       -u1------u2------------u3----
    analyticsMessages ---e1u1--(e1u2 e2u2)---e2u3--
</code></pre>
That&#x27;s a good example, and we fixed that problem with &#x27;errors.withLatestFrom(...&#x27;. But, since we are asynchronous don&#x27;t we also have to worry about this scenario.<p><pre><code>    errors            ---e1-------------------e2--
    userActions       -u1--u2--u3-u4-u5-u6-u7-u8--
    analyticsMessages ---e1u1---------------e2u8--
</code></pre>
Now, let me clarify what happened here. The error occurred after u2, but the errors thread got descheduled and the userActions thread kept on processing. I am not certain exactly what to expect from &#x27;errors.withLatestFrom(userActions,...&#x27; here but I suspect that &#x27;e2u8&#x27; may be the expected output.<p>So this error reporting system is fundamentally unreliable. If this is correct then I would say that combining Rx streams is not appropriate for this use case. This also suggests that although we managed to get rid of our glitches we still produced a terrible piece of software.<p>Do I have to wrong end of the stick? (The answer was yes, but it was good anyway)