This is commonly said by people new to Interface Builder. I don't recall hearing of a long-time Apple / NeXT dev or major app that didn't use it, though.
So why hasn't IB gotten the same amount of improvements and attention as the rest of the toolchain? XCode has come a long way, as have the compilers and instruments.
Oh I don't disagree with you that IB can be annoying, and to a part-time Mac programmer like myself, not as intuitive as I wish. I only meant that the full-timers generally seem to like IB (warts and all), or, even if they don't like it, they still nearly universally use it instead of doing all their layout in code.
The same scenario has repeated itself for many years: a newbie gets annoyed at IB and says "I'm just gonna do it all in code!" and all the graybeards say "ur doin it rong."
I certainly wouldn't embark on a long-term OSX/iPhone project without mastering IB.
It's obvious that your UI is easier to modify and update using IB than hacking it in and out of the view controller code.
Back to the original thread, I do give a little credit to Android to having the option of UI editing done inside of Eclipse. It's not perfect, it's a little hacky, but the concept of slapping down a UI element like a button, naming it, and then having it automatically compile and show up in the editor autocomplete is a powerful thing. The first time it happened it honestly was a nice surprise.
