I actually predict that this will be a major problem for Apple in the future, but probably won't impact their bottom line for their mobile platforms. Pr

I actually predict that this will be a major problem for Apple in the future, but probably won't impact their bottom line for their mobile platforms. Programmers never forget things. They are notorious for not updating basic knowledge they believe and for spreading myths and rumors about technology for decades. I can actually see a situation building where programmers who maybe wouldn't have worked on an iPhone application would still avoid targeting Apple products simply because of the stories about Apple doing "A Section 331" on them. This. Despite my personally benefitting from the new policy change, (I write Obj-C comfortably and will benefit from the reduced competition,) I think Apple is making a grave mistake trying to extend their review checking process in a manner that can only be done in reality by visiting each and every developer. I'm not convinced Apple's in-house analysis tools will be able to capture violations in a manner consistent with their current license wording. It's just going to degenerate into a cat-and-mouse game with the larger and/or more tenacious middleware developers, leading Apple to waste resources and R&D money on license enforcement, driving down profits and adding significantly to the large pile of ill will Apple has accumulated in the last few years. Apple is still living down past quirks and excess of their platforms, like "Cult of Apple evangelism" and "one-button mice," that are no longer true, but hang around their necks like a long decaying albatross. In short, this could help cause Jobs to lose control of his platform's message to the masses if the people able to recommend their hardware and platforms keep sticking "asterisks" to their recommendations.