But instead, iPhone developers are eagerly bending over begging Apple for more because of their myopic obsession with bad APIs, the twin geekgasms of both objec

But instead, iPhone developers are eagerly bending over begging Apple for more because of their myopic obsession with bad APIs, the twin geekgasms of both objecty stuff and C, bloated SDKs, impossible layout mechanisms, and all the rest of the archaic nonsense we’re going to have to rid the mobile Web of in the next few years. It's pretty clear he's never developed with Objective-C, Cocoa/UIKit, etc. if he's calling it a bloated and bad API. UIKit in particular is fresh, clean, and very nice overall, IMO. (I spent years in Javascript/HTML/CSS, moved to the iPhone for awhile and worked on some major projects, and recently started developing an app on Cocoa for OSX - which is a lot more crusty than the iPhone.) I also find it somewhat ironic that he talks about "impossible layout mechanisms" whereas almost every time I've been involved with a webapp I've hit upon some tricky layout requirement that is a pain in the ass because of CSS' builtin assumptions. This part reads like satire...