Re:The Siren Call of KVO and Cocoa Bindings
by lupinglade on Saturday March 15, 2014 @11:57AM
(#7404957)
KVO and Cocoa Bindings are not the same thing. Just because Bindings use KVO does not mean both technologies are alike. KVC/KVO has many uses outside Cocoa Bindings or UI updates. Further, obviously KVC/KVO has a performance penalty and that is exactly why you would not use it for high performance tasks. However for just about everything else it is a great tool and will minimize the amount of code you write greatly, resulting in improved maintainability.
[ Parent
| on HN ]
Re:The Siren Call of KVO and Cocoa Bindings
by mpweiher on Saturday March 15, 2014 @06:54PM
(#7406885)
"KVO and Cocoa Bindings are not the same thing"
Yes. From the Fine Article:
"[..] bindings are one-way dataflow constraints, specifically with the equation limited to y = x1. More complex equations can be obtained by using NSValueTransformers. KVO is more of an implicit invocation mechanism that is used primarily to build ad-hoc dataflow constraints."
Bindings: simple one way dataflow constraints.
KVO: implicit invocation.
Not the same thing.