iPhone SDK: Bittersweet

Well, after playing with the iPhone SDK for a few days, it's going slowly, for two reasons. The first: Apple didn't include a visual designer, so there is no way to build an interface via drag-and-drop.  This is planned (and they demo'ed it), so at leat this will be possible in the future, but it is a tough thing not to have for those of us who are new to building UIs on a Mac OS.  The exclusion of this piece makes a little sense in that it was the only piece of the SDK that was really tied heavily to the iPhone other than the simulator, which you must have, so they probably just ran out of time and made the right call. Second, and way more problematic, is Objective-C.  I kind of "get" Objective-C in that it is basically a set of macros on top of C to help you get some object-oriented features, but man, is it hard to read for someone who knows C++, C#, and Java.  Objective-C definitely took an evolutionary branch off of C that is far different from those other languages and feels like it is stuck in the early COM era of Windows C/C++.  And it is far less productivity-enhancing than C# or Java.  Oh well ... I thought I was done learning new languages, so much for that!