I took your
redux-cycles example and removed the Cycle DSL. It’s basically
sink.HTTP = response$. Not emitting anything here, just adding a description.
Ok, so now that we have established that they both describe the logic. Lets talk about the “chain”. Even though in your image (or Cycle’s devtools) it’s shown as a chain, it’s actually not really a chain. It’s literally a Cycle.
http is the output (sources), the bottom
http is the input (sinks) of your “Steam IO”. If…
I do not want to nit-pick, but didn’t you also specified some control flow in your examples? The
mergeMap etc. is imperative, why isn’t the aforementioned code too?
I am completely sold that having separate streams for I/O and have (in Cycle’s case) sinks/driver to…