I could not even imagine what it is like to be a person for whom Objective c is the normal and being afraid of Swift. :) And I think that's good because, as far as I know, Objective c is still on the plate as your example points it out. :)
Thanks for the books. I put them on my reading list. "Working with legacy code" was already there. :)
It seems like I can't skip the no-storyboard path. I've heard it from a lot of iOS dev that Storyboard just prevents them from being productive. Such a waste. I fell in love with it immediately because it was soo convenient for beginners like me to build interfaces.
And it is! The only thing is the merging conflicts that appear one in a while. If you like to use interface builder, try to use xibs or try to use several storyboards, and not just one :)
Thank you so much for your answers!
I could not even imagine what it is like to be a person for whom Objective c is the normal and being afraid of Swift. :) And I think that's good because, as far as I know, Objective c is still on the plate as your example points it out. :)
Thanks for the books. I put them on my reading list. "Working with legacy code" was already there. :)
It seems like I can't skip the no-storyboard path. I've heard it from a lot of iOS dev that Storyboard just prevents them from being productive. Such a waste. I fell in love with it immediately because it was soo convenient for beginners like me to build interfaces.
And it is! The only thing is the merging conflicts that appear one in a while. If you like to use interface builder, try to use xibs or try to use several storyboards, and not just one :)
I'll definitely look after what this Xib thing is. Today I learned. 🙏👍