The only people I still know that avoid heavy utilization of these do not understand how to properly use them. Go learn!
The only people I still know that avoid heavy utilization of these do not understand how to properly use them. Go learn!
I also agree that the lack of "diffability" for XIBs, despite them being XML, is a pain.
Maybe I was missing something, but my experience matches the OP.
If you're just talking about some buttons in a toolbar, go nuts, but otherwise it's worth the time investment to learn.
That said once you get that base level of understanding, nibs and storyboards are huge time savers, and are the way to go.
I've dealt with far too many bugs involving Interface Builder and it's random changes and "upgrading" the second I touch a nib that it's more of a liability now.
People who say it's less "code" are just delusional. Setting the font in IB versus a single line in viewDidLoad: doesn't save you anything. At some point in time that line of code is getting executed and you will at some point have to maintain it.
I actually consider this a big liability for Apple going forward. The explosion of "phablets" and other form factors spells the end of their pixel-perfect design approach and their tools and APIs for managing dynamic, variable layouts are stone age compared to Android's.
Sure, you can control all your code, but there is so much time that is lost until the UI is finally ready, and than the marketing department wants it redone in one day.