4 ms·

I've got apps that were originally Objective-C and I've migrated parts of the app to Swift and it's been a great experience in almost every respect. I'm honestl

I've got apps that were originally Objective-C and I've migrated parts of the app to Swift and it's been a great experience in almost every respect. I'm honestly surprised at how seamless the experience has been, given that the app is 10 years old and had a pile of very Objective-C specific things (e.g. NSClassFromName or whatever that API is called).

kalleboo 9y ago
On the contrary I've had a lot of problems with the ObjC-Swift interop, to the point where I've mostly given up on integrating Swift into existing ObjC projects. Like most of the other problems with Swift, this comes down to tooling issues. Xcode's "jump to definition" taking me to auto-generated interop header files, "AppName-Swift.h missing" errors, the debugger losing track of a stacktrace in the transition between languages...