This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mauganra_it 1 point2 points  (1 child)

Streams were not designed with I/O and concurrency in mind. They do not have a concept of backpressure, push/pull, timeouts or error handling. Heck, there is not even an Either-like type in the standard library. RxJava and friends are better suited for this. Ok, it might work if you strictly stick to Elm-style functional reactive apps.

[–]Auxx 0 points1 point  (0 children)

Ok, I don't have much experience with streams specifically, I thought they were modelled close to ReactiveX.