Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Streams #13

Open
St4B opened this issue May 10, 2018 · 2 comments
Open

Streams #13

St4B opened this issue May 10, 2018 · 2 comments

Comments

@St4B
Copy link

St4B commented May 10, 2018

I am not in a so good level in using kotlin, so maybe i am missing something, but are not we losing some capabilities by not using streams of data?

@mateherber
Copy link

mateherber commented May 10, 2018

I think the message here is not "do not use rxJava" but "you may not use rxJava solely as a Promise/Future library or for handling threads". If you have use cases which resonates well with data streams I think it is still wise to use rx.

Also kotlin coroutines has great support for rx streams: Coroutines & Reactive

@Zhuinden
Copy link

Yeah, zipping event streams or hiding listeners as Observable (allowing filters and etc) is still good Rx use case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants