Dmitri Zaitsev

>> Can filter be possibly derived from a more general partial reduce, like the normal filter? > No. And strictly speaking the normal `filter` can't be derived from only `reduce`...

@paldepind Thank you for taking your time to answer this. I find it very well written and making a clear point that deserves to be published as blog. People will...

@paldepind >>I find it very well written and making a clear point that deserves to be published as blog. >Thanks a lot for the encouragement. Once we have the benchmark...

@donaldpipowitch > But there's still overhead in just creating that vdom for no good reason if it isn't for diffing. With Turbine's approach there's no overhead of even creating any...

@paldepind Thanks for explaining it so well. It might be interesting to compare with Inferno that apparently "never needs to "diff" virtual DOM": https://github.com/infernojs/inferno/issues/21#issuecomment-165734790 Also the treatment of the `key`...

@paldepind >@dmitriz You're very welcome. Inferno is very cool. I don't know much about it. But, my understanding is that they compile JSX so that they know exactly where data...

@ccorcos @trusktr I have put this probably simplest possible example to illustrate it here: https://github.com/funkia/turbine/pull/48 It does not use any methods, so might be easier to understand. Every `yield` "writes"...

@paldepind ```js const baz = moment((at) => at(booleanBehavior) ? at(foo) : at(bar); ``` >In that example, the baz behavior would dynamically switch between listening to foo and bar depending on...

@paldepind I recall that code was more of a general principle, so yes, there may be errors. Your code may work, where you might need to change the `reduce` method...

That sounds like a long departure from `flyd` :) I can see that you may consider it a less cleaner abstraction, but I think it may help saving a few...