I was wondering the same thing. Reading the other answers, it seems like the reason the author thinks they're superior is that he can design interfaces using on

I was wondering the same thing. Reading the other answers, it seems like the reason the author thinks they're superior is that he can design interfaces using only code. (Not sure if that's the author's point or just the posters here.) I've had to use the apps that result from developers designing interfaces in code and I've had to read some of the code to do it, and in my experience it was all suboptimal. With a tool like Interface Builder (which I'm not saying is good), at least it gives you guides for the standard places that elements should line up with each other. Sometimes you want the baseline of the text of various elements to align. Sometimes you want to ensure the same padding around elements. All of that typically goes out the window when interfaces are designed via code, in my experience. Furthermore, the author seems to advocate that UIs should be disconnected from events. I can't think of a useful UI element that isn't tied to some event. I'd love to learn more about what they mean, but right now, it's not ringing true to me.