I say this in full understanding why Subjects are ...
# rx
d
I say this in full understanding why Subjects are 'non-Rx' in many use cases... but as model fields... it actually seems really useful for achieving 'reactiveness' between otherwise loosely connected parts of an App. I just wondered if anyone had positive experience following this pattern, or it has been avoided either a) because it has identifiable downfalls or b) just because a 'subjects are bad' dogma (in which case that might bear challenging).
c
a) because it has identifiable downfalls
A Subject being both an Observer and Observable causes tight coupling
Subjects aren’t bad
they should just be abstracted away
Observers should not know that they are observing a Subject
So an encapsulated Subject is fine
👍 1