Apple doesn't really want developers for the iPhone. You want proof, you say? Interface Builder - the worst piece of crap since BEFORE Borland's tools for C++ back in Windows 3.0 days. I could at least build a window that would display what I told it in the GUI without writing code, whereas if I try to use a proper UIView, UIViewController, UIWindow, and throw in a UILabel it doesn't work. Half the time it crashes, the other half of the time the window's blank and doesn't actually display the UIView at all, even though I've double-checked my 'linkings' that IB likes to use. If I could use C#/.Net, my LiveJournal client would ALREADY be ported and done by now (I've already got code that does the LJ client stuff). I ported a bit of the backend code over to Objective-C, but then when I went to write the UI I ended up wasting 4 HOURS of my precious time today that I got to myself - as a dad I don't get a lot of time to myself without having to watch the bug, and I really feel like Apple doesn't want the casual programmer (who nonetheless, without tooting my own horn much, has enough experience to manage in most programming languages) programming on the iPhone. I like the UI itself, but programming it is rather non-trivial, and very frustrating.