I "learned" RxPy in a couple hours yesterday (a 3rd party lib I'm using has an interface that requires me to use them), and I figure I'll share a bit about my e

I "learned" RxPy in a couple hours yesterday (a 3rd party lib I'm using has an interface that requires me to use them), and I figure I'll share a bit about my experience: 1) the documentation is supremely lacking (subjects aren't even mentioned in the RxPy repo https://github.com/ReactiveX/RxPY https://github.com/ReactiveX/RxPY) 2) the generic documentation points to language specific documentation – that's 80% just "TBD" (http://reactivex.io/documentation/subject.html http://reactivex.io/documentation/subject.html) 3) it's actually quite simple once you figure out it's just code level pub/sub with a new naming convention. 4) there seem to be some opinionated perspectives around using it in the community, though largely from a JS perspective (look into "should I use subjects"). Despite those flaws, I've found it pretty accessible, and I'll actually switch out some home-grown code for it. [edit] I noticed some other comments complaining about execution handling (threads, etc.) so I figured I'd update this and say, maybe I got lucky as it's all pretty straightforward in Python (as long as you understand your app's execution environment (threads, asyncio, etc.) -> https://github.com/ReactiveX/RxPY#schedulers https://github.com/ReactiveX/RxPY#schedulers