I'm not an iPhone developer, but I am surprised how many of them here think they're being helped out by this. I see it as a step to hinder them (this is modifi

I'm not an iPhone developer, but I am surprised how many of them here think they're being helped out by this. I see it as a step to hinder them (this is modified from another comment I wrote a couple of days ago...): 1. Apple are increasing the barrier of entry for iPhone devs in to OTHER mobile development worlds - they're no longer able to develop a solution that is easily portable to Android, WinMo, BB, for example. They're forcing devs to bet their ability to write popular mobile apps on the fact that Apple will always provide the platform they need, and (more worryingly) that they will continue to keep the App in the App Store. If Apple chose to duplicate the functionality of any app themselves, the developer can't easily move to providing it for Android - so they're screwed. Given how Apple don't seem to care about doing this, I think it's bad for iPhone developers' job security. 2. There will be more ObjC devs now, so iPhone developers' hard earned ObjC skills will be less unique and useful in the long run. If, however, the move results in a working ObjC-->Other platforms compiler, point 1 becomes less important.