XStream.js & diamond pattern about laminar HOT 3 CLOSED

Thanks for checking in xstream; both libraries work in similar fashion.

Sorry for the misunderstanding, but the combineLatest with multiple updates is not a problem in outwatch itself. But more of a problem we observed, when building an application on top of rx.js. This also lead us to further looking into state management vs. event streams, here we are working with scala.rx currently. We found that it is quite easy to introduce glitches with inconsistent data when just working with streams and its operators. We surely could construct it differently as also discussed in the link, but this might be error-prone and easy to overlook as I need to reason about the origin of each stream when I am combining. Or am I missing something?

from laminar.

Ah, I thought you were concerned about the briefly-incorrect state of the snabbdom node and/or the extra calls to snabbdom's patch method.

I'm still yet to fully process what Felix wrote about state vs events. I understand the difference, but didn't quite visualize the practical implications of having two systems yet.

from laminar.

Fixed in #8 with the magic of Airstream, so XStream problems are not relevant anymore. That PR will be the next version of Laminar soon.

from laminar.