Dmitri Zaitsev

Thanks @davisonio for extensive comments! > I don't think that timestamping is the best possible option though, as @sindresorhus rightly pointed out. Just so it doesn't get lost in the...

Here is a reddit thread illustrating how much people care about timestamps :) https://www.reddit.com/r/reactjs/comments/431oat/webpack_for_react_the_complete_and_uptodate_guide/

According to https://github.com/paldepind/flyd#flydonfn-s, the `on` method is essentially a "worse" version of `map` as it does the same but does not return anything useful. And if you use `map` instead...

@StreetStrider Aren't they meant to fire simultaneously?

@StreetStrider All at the same time, as soon as their parent emits.

@StreetStrider The order is not guaranteed by the spec. It may depend on the implementation and on the runtime environment. Why does it matter?

Many thanks @paldepind for taking your time to comment! > To me s(s1) reads as "send the value s1 into s". That is exactly my intuition and was the very...

I would add my vote to support the fluent version. I found it for instance, more elegant to write `stream.scan(reducer, initVal)` than `scan(reducer, initVal, stream)`, it looks cleaner separating the...

@paldepind What about transforming the `flyd.stream` factory into new one creating all its streams objects with the same prototype object `protoObj`? Then you would set all the instance methods on...

This is the working code (with tests passing): ```js /** * Set prototype object for all instances created by the Factory * (can be used to provide additional instance methods)...