{"id":27842,"date":"2020-01-10T14:47:19","date_gmt":"2020-01-10T19:47:19","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=27842"},"modified":"2023-02-10T10:44:53","modified_gmt":"2023-02-10T15:44:53","slug":"kvo-my-enemy","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/01\/10\/kvo-my-enemy\/","title":{"rendered":"KVO, My Enemy"},"content":{"rendered":"

Brent Simmons<\/a>:<\/p>\n

\n

One of the keys to the stability of the shipping versions of NetNewsWire is that we don’t allow KVO (Key-Value Observing).<\/p>\n

KVO is a false convenience — it’s often easier than setting up a delegate or old-fashioned notification. But to use KVO is to just ask for your app to crash.<\/p>\n

And not just crash, but crash in hard-to-figure-out ways.<\/p>\n<\/blockquote>\n\n

Drew McCormack<\/a>:<\/p>\n

As others point out, there are a bunch of issues with the FeedlyOperation class, such as the isAsynchronous override, and not changing to the final state atomically. But I think maybe the biggest problem is the use of Swift key paths. Not sure if that should be supported, but in my testing, it doesn’t work. Changing to strings for the key paths fixed things for me.<\/p><\/blockquote>\n

I’m not sure what the issue is—perhaps a Swift bug or incorrect property declarations so that there’s disagreement about whether is<\/code> is part of the property name—but Swift key paths seem to be a common source of problems.<\/p>\n\n

Brent Simmons<\/a>:<\/p>\n

We’re going to write a replacement for OperationQueue. <\/p><\/blockquote>\n\n

Previously:<\/p>\n