I wrote an article to explain why so many people hate KVO. sandofsky.com/blog/kvo.html
Conversation
KVO and NSNotificationCenter are not the only tools. NSNC means writing a ton of boilerplate. We can do so much better with Swift
1
2
we can write an explicit API that encapsulates current value + observation of changes. RAC has this:
Quote Tweet
Just released: @javi's Swift Summit SF talk
Happy Friday! skilled.io/javiersoto/sim
Happy Friday! skilled.io/javiersoto/sim
2
4
Maybe that works. I know Notification Center works, its issues are known, and if anyone joins my team, no training required.
3
1
3
7
for sure. I actually didn't even want to advocate for RAC, but I believe just the Property API is easy to...
1
replicate and is worth it considering how often this pattern is used in iOS apps
1
1
Replying to
yeah. but… I think the very idea of observing properties might be an anti pattern, for all the same reasons.
Replying to
maybe sometimes. But what I think is an antipat. is exposing a simple getter for a value that changes over time
2