This is a demonstration of how members-only content will appear to your subscribers.
I plan to introduce additional menu items to make it easier to navigate to the relevant category. Below, you'll find an excerpt from one of my articles.
For this test, I'm restricting this section exclusively to members.
Rule 1
- Every Observable is inherently lazy—no exception to this.
Rule 2
- Observables can be classified as cold, which provide a unique execution context to each subscriber in a unicast manner.
- Alternatively, they can be hot, which share a single execution context across a group of subscribers, doing so through a multicast approach.
Rule 3
- A Subject functions as both an Observable and an Observer.
- The Observable side operates in multicast mode, yet its execution remains deferred until the initial subscriber arrives.
- The Observer side is set up eagerly, permitting you to invoke
.next()to push data through the Subject. - Having the Observer side does not mean the Observable's execution context is active prior to the first subscription.
Rule 4
- Certain Subjects, such as
BehaviorSubjectorReplySubject, are stateful and extend the capabilities of the Observer side. - These Subjects can hold a history of 1..n prior states, which the Observable part then delivers to any new subscribers.
After reviewing this, do you consider RxJS to be a challenging subject, pun fully intended? :D
The Angular Team has voiced intentions to possibly make RxJS optional down the line.
Would you prefer for RxJS to remain a required component?
Or is making it optional the better approach?