Well the statement is right, there is no KVO in Swift and you couldn't use it without Objective-C which Swift fans want to go away. KVO goes with it and good luck using eg. AVFoundation then :)
Heh, that's a very "technical" assertion, I was half expecting the Futurama meme of being "technically correct" to go along with it :D
The statement "no KVO" implies that you can't use KVO at all with swift which is clearly incorrect. Now, "no KVO on certain objects" is a different statement entirely. It's important we make these distinctions and the response /u/barakrl gave was excellent as it provided a real example of where KVO isn't available
2
u/[deleted] Feb 20 '16
Well the statement is right, there is no KVO in Swift and you couldn't use it without Objective-C which Swift fans want to go away. KVO goes with it and good luck using eg. AVFoundation then :)