Yassine Elouafi

Thanks for your feedback. The main reason I didn't consider style based solutions is because I use some css-only features (`@font-face`, pseudo selectors). But theme-integration with redux devtools is an...

The saga monitor uses its own internal store (not the app store). The monitor is connected to the saga middleware and receives monitor events directly from it (not via redux...

the action object is stored from [here](https://github.com/yelouafi/redux-saga-devtools/blob/master/src/store/createSagaMonitor.js#L88). We also compare by ref [here](https://github.com/yelouafi/redux-saga-devtools/blob/master/src/store/selectors.js#L72) to find sagas who took an action. If a unique id should be assigned to actions, I...

yeah actually there is no automatic management for child forks. The above use case could be solved manually (but less elegantly) ```js const subtask = ... const task = Task.from((resolve,...

Actually not. But I think defintely worth adding it

There is a fundamental diff between discrete event streams and behaviors. A behavior has _always_ a value. You may emulate some semantics of behaviors with scan/when but behaviors are more...

The closest concept to behaviors is actually bacon Properties. But AFAIK bacon doesnt support dynamic dependencies (useful to build computations based on a behavior of an array of behaviors)

I think lifting is more related to the applicative structure. And both Events and Behaviors are Functors, Applicatives & Monads. But each concept has different semantics for the those structures....

Cf the example of allDone in todoList (see readme). How can you express that behavior using just map an ap?

@mweststrate I think what you call TFRP is the perfect expression of implicit (or call it dynamic) lifting. The main purpose of lifting is to promote behaviors as first class...