Thanks for the response; I’m pleased that you found the article informative. I’m the article’s author; Maxim is the editor of the article’s publication: Angular in Depth.

Interestingly, the history of the article’s publication is related to your questions. Originally, it was published as a stand-alone Medium story and I was hesitant to accept Maxim’s offer to include it in Angular in Depth, as RxJS is not an Angular-specific library. I later changed my mind. There were a number of reasons for this: Angular is heavily dependent upon RxJS; there are topics that I want to cover in future articles that will be Angular-specific; Maxim pointed out that some of his articles in the publication are Angular-related, but not necessarily Angular-specific; and I expected the articles to reach a larger audience if included in Angular in Depth.

Anyway, RxJS is not Angular-specific and — apart from a polyfill for Symbol(observable) — it has no dependencies. And, if you consume only the parts of RxJS that you actually use, it is a small library.

To answer your question about where I use it: pretty much anywhere I’m working with asynchronous code. If you are unsure of where you should or could use it, Andre Staltz’s The introduction to Reactive Programming you’ve been missing might help with your understanding of RxJS and where it can be used.

You can definitely use it with React. In fact, there is RxJS-based middleware for Redux: redux-observable.

Similarly, there is an RxJS-based Redux implementation for Angular: ngrx

Basically, if I’m building an app, I will be using Redux — either with React or with Angular and ngrx — and I will be using RxJS.