4 ms·
The OS and built-in apps have tighter performance requirements than third party apps. I'm guessing Swift needs to catch up to Objective-C in heap and CPU usage
by Aleman360 11y ago
The OS and built-in apps have tighter performance requirements than third party apps. I'm guessing Swift needs to catch up to Objective-C in heap and CPU usage before it's considered.
- seivan 11y agoWho module optimisation for generic code. Getting rid of dynamic dispatch when setting classes as final can do a amazing things when it comes to performance. Obj-C would have to dispatch out to C/Obj-c++ for that, now you can use Swift. Although Objective-C got nullable arguments, it still isn't as safe as Swift. You're always a null pointer away from a crash... or unexpected behaviour as calling shit on nil doesn't matter