Alex

> That's what we're discussing here, whether to do the original proposal by Jan, or to do something like invoke operator, sending to sinks. Proposed `invoke()` API is actually the...

@staltz > how is invoke the same as events `DOM.invoke('blur',..)` - changes the state of the element and `DOM.events('click', {preventDefault: true})` - actually change the state of the element causing...

I don't see any reason for additional drivers here, this is an unnecessary complication. `Blur` effect is just DOM effect that removes cursor/focus from the element. I really don't see...

@aronallen I really don't see a reason to introduce new entity ( a driver that does DOM "effects"), this is all can be done using current API. It is not...

```ts function main(sources) { return { DOM: sources.HTTP.get("/whatever") .map(view) .startWith("loading") }; } ``` Is there really a problem of implementing this in the context of "current architecture"?

> If we want to preserve the property where all write effects (and HTTP requests) can be inspected or intercepted via the sinks of the app, then yes, the current...

So `applyAPI(child)` - is a plugin/driver specific thing? Something like could be achieved with current run/drivers too, I believe. There would good to see just a code snippet for this...

@jvanbruegge how is it going with neo? I've got a question. > A driver is responsible for interpreting a stream of commands and returning a stream of data by doing...

I belive everthying works as expected. You can add this: ```ts const ab = xs .combine(a, b) .map(([a, b]) => Math.random()) .debug('ab') .concat(xs.never()) .remember() ``` With this you make `ab`...

> The promise of reactive programming is that your program becomes much more predictable and less susceptible to incorrect behavior caused by unexpected sequences of events. I believe there is...