5 ms·
I'd say #1 isn't an Objective-C issue, but a Cocoa issue. Do not tarnish the wonderful language with the terrible framework. :)
by skylan_q 14y ago
I'd say #1 isn't an Objective-C issue, but a Cocoa issue. Do not tarnish the wonderful language with the terrible framework. :)
- camus 14y agoI thought Cocoa was pretty good, what makes you think it is terrible ?
- myko 14y agoSame here. I think without Cocoa I wouldn't like Objective-C much at all.
- borgopants 14y agoCocoa is pretty good, but like all frameworks, it definitely has its downsides. Point #1, unfortunately, seems to be something that the author has a hangup about. I find that using a single XIB for a view controller at a time works the best for me, and maintains some semblance of MVC. I work on a relatively large app, with more screens than usual, and I never find it hard to figure out view controller transitions or anything like that.
- rimantas 14y agoI think it is worth mentioning that there is Cocoa and there is Cocoa Touch: supposedly saner and cleaner version. I am only familiar with the Cocoa Touch so I cannot compare myself.