Comment Re:[sigh] (Score 1) 457
That's a pretty myopic view. Other app translation layers are going to be knocked out of the market too.
To Apple that is just unfortunate collateral damage. Regrettable, but the enemy must be eliminated. And that is my point.
You can't develop for a game console without using the certified tools from the console vendor, and paying out the ass for the privilege. Prior to the iPhone, there were plenty of phones and platforms with even more draconian restrictions. Any app for any phone on Verizon Wireless required code to be written in Java.
So porting your iPhone app to another platform isn't much of an issue anyway. Unless the other target platform restricts you to Java.
In essence Apple's updated section 3.3.1 policy would require you to manually retype and reprogram your application unless it was originally written in one of Apple's approved languages. I doubt very few if any of the vendors that required the use of their development tools actually specified how that code got written - even if it was Java. As long as it was in their approved language utilizing their specified APIs. Whatever the target language requirements the code could still be generated from another language - except in the Apple iPhone/iPad world.
Again the target was absolutely Adobe Packager in this case. It will hurt others, but they would never haven enacted this policy without the Packager.
I'm not sure why this "bloatware" argument came up here. The generated code may or may not be more "bloated" than a hand generated program in the approved language. I'm sure many of the existing hand written apps in the App Store are not shining examples of efficient, tightly written code. Any apps generated from ActionScript or another language/platform would require the same approval from Apple before being released into the store.
And Apple will continue its war on Adobe with the slavish approval of the Apple fans.