is KVO still "broken"?

Question

I let down KVO pattern since I read this : KVO vs NSNotification vs protocol/delegates?, where it uses a hard word : "broken", refering to an interesting article from Mike Ash relating three API design problem in 2011.

I can't find any news after that year. How did KVO evolve ?

score 0 · Accepted Answer · answered Aug 13 '15 at 15:40

0

When Mike Ash says KVO is broken, he isn't talking about if it works or not. Ash is saying that the API is designed badly and this bad design limits what developers can do with it.

A better use of "KVO-esque" programming can be found in libraries like ReactiveCocoa.

If you want to learn more check out these links.

answered Aug 13 '15 at 15:40

72A12F4E

1,744
1
14
28

Yes, I forgot the quotation marks... – Jan ATAC Aug 13 '15 at 15:43
Thanks for your answer and the links. This one suits me better : https://www.mikeash.com/pyblog/key-value-observing-done-right.html – Jan ATAC Aug 13 '15 at 15:48
1

A really nice (more modern) library for dealing with KVO is [KVOController](https://github.com/facebook/KVOController) – joerick Aug 13 '15 at 15:52

is KVO still "broken"?

1 Answers1