News for hackers. Stuff that matters.
Re:Why Apple did what they did by rimantas on Saturday April 10, 2010 @01:03PM (#1255312)
I get the point about Adobe, but Android?
Re:Why Apple did what they did by jamesk2 on Saturday April 10, 2010 @01:17PM (#1255344)
Flash could have made it easy to target iPhone and Android with very similar code bases.

Now, developing for one, doesn't making porting to the other so simple.

It forces small developers to ask: bigger market or open market?

Re:Why Apple did what they did by binspace on Saturday April 10, 2010 @03:31PM (#1255551)
I really hope the open market (Android) wins this. I'm not looking forward to Steve Job's (similar to Bill Gates') vision of the marketplace.
Re:Why Apple did what they did by astine on Saturday April 10, 2010 @01:13PM (#1255331)
Using translators it would be possible to create a sort of meta-platform that could compile to both iPhoneOS and Android. A clever developer could make an SDK that abstracted the differences in the platforms and made it easier for developers to support both platforms by using the same codebase for the same apps on either. By making it more difficult to support both at the same time, Apple may be hoping to keep more developers on only their platform and retain the edge that they have over Android.
Re:Why Apple did what they did by lehmannro on Sunday April 11, 2010 @09:03AM (#1256783)
That's what quite a few programming platforms already do (I know it's the case with Appcelerator and suspect MonoTouch doesn't do it any differently); but these are actively outlawed by the new paragraph 3.3.1: (emphasis added)

Applications must be originally written in Objective-C, C, C++, or JavaScript.

Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited.

Re:Why Apple did what they did by JamieEi on Saturday April 10, 2010 @03:35PM (#1255558)
Makes it harder for people to port apps to Android if they are written in Object C. Apple figures that the iPhone is priority #1 for everyone developing a mobile version, so they can use their TOS to raise the cost of supporting priority #2.