@etorreborre
Software engineer in search of a galaxy brain
Software engineer at the intersection of functional programming, product development and open-source
Nothing here yet.
Great, I didn't know that! I can see that there's indeed some space for providing other Encoder s with different outputs. I haven't seen it applied to a direct ByteString encoding though. I suspect that this might change the Encoder interface a bit to be closer to what is presented in my post and in aeson . Actually even with aeson I don't understand why list is not taking Series as a parameter: https://hackage.haskell.org/package/aeson-2.2.1.0/docs/Data-Aeson-Encoding-Internal.html#v:list.
Aren't these the same thing? With streams, the place where you connect a publisher and a subscriber is explicit. With actors, the fact that actor A publishes some information to actor B is hidden inside actor A. Also, I'm not sure what you mean by "actors have to know about each other" but Akka has adapted response interaction pattern I was talking about having to know about each other references. Thanks for the pointer on the adapted response pattern. I see how it can be helpful. But that is a lot of ceremony for my taste!
