3 ms·
Yup; 2015 was not the right time to move to Swift for most people. If I started a new app today, I'd use Swift -- it's mature enough. But in 2015 and for a lon
by KerrAvon 3y ago
Yup; 2015 was not the right time to move to Swift for most people.
If I started a new app today, I'd use Swift -- it's mature enough. But in 2015 and for a long time after, it wasn't really a good option unless you wanted to be on the bleeding edge (and you were willing to bleed).
Compile times will always be slower than Objective-C, but the compiled code _can_ be faster, with effort. And maybe someone will eventually break down and write a Swift-centric debugger.