> The choice to use Swift comes with some tradeoffs, and it appears that Apple has decided it’s generally not worth it for their apps or frameworks yet. Really

> The choice to use Swift comes with some tradeoffs, and it appears that Apple has decided it’s generally not worth it for their apps or frameworks yet. Really, that's your take-away? > However, there could be a very different story building for iOS 10. Since most of iOS is only dropped once per year, we’ll just have to wait and see in June. AHHH! You almost get it. Apple needs time to make the change (and they'll most likely never completely change over to all Swift) for most of the apps they decide to change. They want a nice fluid experience for their customers. Product cycles aren't short, iOS/OS X are at once per year, but that doesn't mean that some changes to them aren't planned out for much longer than a year.