CommentComment

I've (finally) had the chance to get my hands on the new predictive code completion in Xcode, and while it sometimes does exactly the right thing, it also often gets it completely wrong, and I find myself throwing away most of the code it generates.

I have to agree with Stewart in that it might be useful for some very narrow use cases, but it might actually better to turn if off if you're trying to properly learn how to code in Swift.

Overall it feels like this feature is more a waste of time than a time saver.

It is quite interesting to observe how the love/hate relationship a lot of developers have with Xcode is slowly resulting in third party IDEs becoming more and more attractive for Swift and iOS development - in this issue of Not only Swift, I included some interesting articles that show how you can use third party IDEs to better integrate with AI coding tools.

We've seen this before with IDEs like Eclipse (which initially was created to challenge Microsoft's Visual Studio, and then got eclipsed by IDEs like JetBrains IntelliJ). Will Apple be able to turn things around for Xcode, and win back the love of the developer community?

Let me know what you think - you can tweet at me @peterfriese, or just reply to this email.

Thanks for reading,

Peter  

SwiftSwift

SwiftUISwiftUI

Swift on the ServerSwift on the Server

AI and ML



Productivity

Podcasts

Fun stuff