My current plans for Swift adoption in 2015: I’m just finished a contract project in Swift 1.2. It was a really great experience for working through Swift and finding it’s strengths and weaknesses. At work, we may introduce some Swift 2.0 into our application for new source, but there is currently no pressing need to transition anything existing. Our library we ship to other developers will continue shipping in Obj-C. There are currently no plans to...
Continue reading...Swift
Obj-C and Swift, not Obj-C vs. Swift
On Twitter, I’ve been vocal that I don’t believe Obj-C is going away any time soon. For reference, Apple’s stance on the matter is: “Objective-C is not going away, both Swift and Objective-C are first class citizens for doing Cocoa and Cocoa Touch development.” It’s important to note that while there are a lot of community websites stating that Swift is the replacement for Obj-C, that has never been any sort of official position from Apple. This “There...
Continue reading...Why I’m Not Adopting Swift (For Now)
If you follow me on Twitter, I’ve made a lot of noise about how I don’t think developers should be adopting Swift in it’s current state. My problem isn’t with the idea of Swift, or replacing Obj-C. I believe Swift could, in the coming weeks or months become a language suitable for writing production code. But I don’t believe it is such a language today.
Continue reading...