Does the Builder interface use me?

Question

I am new to Cocoa. I talked to my brother, who built several iPhone apps, and I said something about Interface Builder. He said he was not using it - he was programming his user interfaces. He said that in this way he does not need to worry about loading the NIB. I understand that using Interface Builder actually creates instances of view / window / button / etc objects that are serialized and need to be deserialized when the application loads, but is deserialization expensive? Of course, he talks about the iPhone, and I'm developing on the MacBook Pro, but still.

Answer 1

I have yet to see an argument against using IB due to performance reasons, and using both methods, I did not see any differences anyway. For more intensive applications, I usually do not use IB just because it is difficult to create complex individual views with it. Therefore, as a rule, I use IB for simpler applications and adhere to a pro-game approach to more complex applications. This approach obviously also optimizes performance.

Answer 2

IB! . , . ( ), , , FAR (IB) .

Answer 3

, Apple; Interface Builder (IB). ( , ;)!), , Apple ( Cocoa Bindings...), .

, IB ( ), - very; li'l, . ( , .) , , IB.

Answer 4

Interface Builder - , NeXTSTEP, - (IMO) . Aaron Hillegass , " Cocoa NIB. ".
: " "

Answer 5

. , ERP / Interface Builder.