Trying to justify using RxKotlin on top of RxJava ...

# rx

[liminal]

Trying to justify using RxKotlin on top of RxJava 2. So far I like the plusAssign operator to add to CompositeDisposable as well as clarity of writing out of onNext, onError, etc. anything else that you like? I wonder how RxKotlin will affect RxJava 2 to RxJava 3 conversion

[louis993546]

subscribeBy is nice 👍

[Kev]

https://github.com/ReactiveX/RxKotlin#Extensions

[Kev]

Most of them are pretty handy

[alexsullivan114]

Also it makes using zip and other combining operators a lot easier. I've spent a lot of time trying to figure out why the hell Observable.zip isn't compiling in Kotlin. Using the Observables namespace handles it easily.

[alexsullivan114]

Somewhat tangential, but I think RxKotlin is a poor name for the library. It causes endless confusion

[louis993546]

yea, there is a thread for 2 years now about that: https://github.com/ReactiveX/RxKotlin/issues/115
and it looks like badoo actually went ahead and do it themselves: https://github.com/badoo/Reaktive

[ursus]

Just try combineLatest without rxkotlin

[liminal]

i am a little scared of rxjava 2 to 3 conversion while rxkotlin is used. the conversion that will need to happen in the next year and a half

[ursus]

what is so different?

[alexsullivan114]

As far as I can tell, the primary change for RxJava3 is that different portions of the library are being split off into different modules. That should be an easy update for the RxKotlin maintainers to add.