I switched to almost pure swift for a new app after having worked with obj-c a couple of years ago. TBH, when I first encountered swift I hated it, mostly becau

I switched to almost pure swift for a new app after having worked with obj-c a couple of years ago. TBH, when I first encountered swift I hated it, mostly because I felt it was always nagging me about optionals coming from rather fast and loose obj-c code. I eventually embraced it and the new App greatly benefitted, hardly any bugs out in the wild compared to our other apps, we mostly just get crashes from Apple code. Code is reeadable and easy to understand (although there is still some terrible code in the app from when I was still getting my head around it, but it works fine). It has some frameworks and protocols I've started to use extensively, the codable protocol is especially useful for web interface, combine is coming on in leaps and bounds. I still don't trust SwiftUI, even Apple's demo projects don't always implement things correctly and don't display properly if you use the wrong device in the wrong orientation. So I still use IB (New swift developers don't like it, it is a pain and hard to use for apps that run on all devices in multiple orientations, but for what it is, I've used worse in my career)