Dynamic Swift
Not sure I see what&#x27;s going on here (it&#x27;s just a blog post linking to other blog posts?), but is this arguing that Apple should turn the safety of Swift back into the unsafe mess of Objective-C? Horrifying stuff like swizzling, respondsToSelector tricks, etc.? That&#x27;s what Swift is trying to get away from!<p>Some of the classes in Apple&#x27;s frameworks <i>need</i> to be overridden, some of them cannot be overridden, some of them don&#x27;t both to call their overridden accessors - it&#x27;s a mess! You can only discover this stuff by reading the documentation (if it&#x27;s even there), when it ought to be enforced by a strict compiler.