Discussion Episode 14: RxJava — the Present and Future with David Karnok (core maintainer)

[sockeqwe]

No description provided.

[artem-zinnatullin]

What about "Episode 14: RxJava — the Present and Future with David Karnok (core maintainer)"?

[sockeqwe]

Makes sense 👍

[dhartwich1991]

Hey guys :) You mentioned that one should generally not use Single.just() if I understood correctly. Could you sum up exactly why? I think I didn't fully get it :) Thank you for the great show! I really enjoyed listening to it.

[akarnokd]

@dhartwich1991 Artem, his colleagues and one user per month on StackOverflow wants to use just for dynamically computing values but whatever X you have with just(X), that reference is constant and already computed, thus any subscriber to just will receive the same "old" reference.

I talked about this oddity and compared it to println(X) where everyone understands X has been computed before the invocation of println.

Artem suggested deprecating just and promoting fromCallable and I responed with legitimate use cases for just inside startWith or defaultIfEmpty and I mentioned it is a matter of educating users who have that misinterpretation I mentioned in the beginning of the comment.

[PrathamKesarkar]

@sockeqwe Hey hannes,I cloned your DroidConBerlin repo. Actually I haven't worked with the kotlin much so I just wanted to ask you how would your code provide Stub Scheduler for testing such as Scheduler.immediate() .

[sockeqwe]

Hey @PrathamKesarkar let's continue this discussion in the droidcon Berlin repo. Just copy your previous comment over there (as a new "issue")