If you're anti-KVO, why? Let's set aside performance (which is improving) and the single-method-name. Interested in architecture gotchas.
Conversation
Replying to
The observer pattern, used without care, encourages more un-tree-like control-flow / data-flow graphs.
Replying to
(with the corollary being that more tree-like graphs are more isolated, predictable, interchangeable, etc)
1
7
Replying to
It is very possible to use the observer pattern in a tree-like fashion, e.g. if the observed object is a subtree’s “root.”
2
Replying to
This. I have seen some real KVO-driven, side-effect-laden maintenance nightmares in consulting.
1
5
Yep. I only use KVO as an implementation detail behind an observer with a clear target and delegate cbacks.
1
Yep, there are various tactical concerns including serious perf overhead, async unpredictability, etc. Those are fixable.
1
Show replies
Replying to