>i don’t think you even understand what corouti...
# rx
a
i don’t think you even understand what coroutines are, because they are literally the same thing that’s already in RxJava
not sure how you got to that point, what I was saying is that RxJava owns this part of implementation and can achieve higher performance by the cost of worse api that seems to be used rarely by users of the library.
not only did i not bring that up again, but someone still has to write operators
that was simple assumption based on previous conversation.