So, again, I’m documenting the problems currently solved by
Objective-C’s dynamism, and suggesting that Swift, as it evolves,
needs to take these problems into account. The foundation should
be built with some idea of what the upper floors will look like.
The answer doesn’t have to be that Swift is dynamic in the way
Objective-C is, or even dynamic at all. But the eventual Swift app
frameworks need to solve these problems as well as — hopefully
better than — UIKit and AppKit do right now. And those solutions
start with the language.