Why are Subjects not recommended in .NET Reactive Extensions?

Question

I am currently getting to grips with the Reactive Extensions framework for .NET and I am working my way through the various introduction resources I\'ve found (mainly http:/

Answer 1

It is bad to generalize that Subjects are not good to use for a public interface. While it is certainly true, that this is not the way a reactive programming approach should look like, it is definitively a good improvement/refactoring option for your classic code.

If you have a normal property with an public set accessor and you want to notify about changes, there speaks nothing against replacing it with a BehaviorSubject. INPC or additional other events are just not that clean and it personally wears me off. For this purpose you can and should use BehaviorSubjects as public properties instead of normal properties and ditch INPC or other events.

Additionally the Subject-interface makes the users of your interface more aware about the functionality of your properties and are more likely to subscribe instead of just getting the value.

It is the best to use if you want others to listen/subscribe to changes of a property.