Is there a general consensus that Streams2 in Node.js are for byte data and not arbitrary objects? cc @izs @dominictarr @Raynos2
-
-
Replying to @mattpodwysocki
@mattpodwysocki@dominictarr@raynos2 IMO, streams have always been awkward for arbitrary objects. Streams2 supports em, but still awkward.1 reply 0 retweets 0 likes -
Replying to @izs
@izs@dominictarr@Raynos2 hence why I'm focused on backpressure in RxJS to get the best of streams but arbitrary objects1 reply 0 retweets 0 likes -
Replying to @mattpodwysocki
@mattpodwysocki@dominictarr@raynos2 You CAN use the objectMode:true flag in streams2. It works, but it is awkward, like I said.1 reply 0 retweets 0 likes -
Replying to @izs
@izs@dominictarr@Raynos2 well, streams are good for linear, but for CEP, streams of streams and partitioning/aggregations gets difficult2 replies 1 retweet 1 like -
Replying to @mattpodwysocki
@mattpodwysocki@izs@dominictarr@raynos2 I diverged for this reason - CEP use cases need more flexibility w.r.t branch, join, ...1 reply 0 retweets 0 likes -
Replying to @darachennis
@darachennis@mattpodwysocki@dominictarr@raynos2 Yeah, these things should be built atop streams, not squashed into 1 dimension.1 reply 0 retweets 0 likes
@izs @mattpodwysocki @dominictarr @Raynos2 Yup. There's some discontinuity thought between IO and compute/analytic streaming though IMHO
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.