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

Support for rxjava 3 #46

Closed
D00mch opened this issue Jul 13, 2019 · 3 comments
Closed

Support for rxjava 3 #46

D00mch opened this issue Jul 13, 2019 · 3 comments

Comments

@D00mch
Copy link

D00mch commented Jul 13, 2019

Hey! Are you going to support rxjava 3.x?

@niwinz
Copy link
Member

niwinz commented Jul 13, 2019

yep, i don't start working on it bu it is on the roadmap

@niwinz
Copy link
Member

niwinz commented Sep 21, 2019

On the end I think that for the 6.0.0 I completly remove the clojure part.
I don't have a good uses cases for rxjava on jvm (having core.async and manifold). Handling backpressure in rxjava and clojure is... not idiomatic. It is not worh the effort of maintaining it.

On the cljs part i using it a lot on many projects and i want to focus on the real use case.

@niwinz niwinz closed this as completed Sep 21, 2019
@jconti
Copy link
Contributor

jconti commented Sep 25, 2019

I would be sorry to lose support for beicon on the JVM, but I would not be sorry to loose rxjava. If it was all implemented with core.async, that would suit me fine. The expressiveness of reactive streams is superior to plain core.async IMO. And I think beicon.core/to-atom is superior to approaches that define "cells" with "automatic" updates. Just my 2 cents. Beicon is one of my favorite libraries.

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

No branches or pull requests

3 participants