3 ms·
Most of these all sound like improvements to XCode, not Swift?
by Andrex 7y ago
Most of these all sound like improvements to XCode, not Swift?
- cableshaft 7y agoI guess I should say "My experience in working with Swift has come a long way", because XCode being so crap with it made it a pain in the ass to code in Swift back then, for me, especially considering how rock solid Visual Studio is in comparison. To be more specific about Swift, though, there used to be a ton of things you had to bridge to Objective-C in order to do back then, and now it seems like there's almost nothing you have to bridge to Objective-C to do unless you want to work with your legacy code (all of their libraries now have Swift support, at least those that I use), and there's now a cool new SwiftUI framework that is very easy to use and very powerful.
- saagarjha 7y agoSwift is quite strongly tied to Xcode because most people use it and that’s where Apple puts most of its tooling effort.