How many people upset over Apple's rules are actually iPhone developers?
wallflower: I have a Java/Flex background, and I have spent the last four months (approximately 300hrs) fully invested in learning Cocoa/Objective-C. I love Categories and Protocols. NsNotificationCenter is beautiful. Cocoa is design patterns in real-life. Instruments is amazing. IB doesn't suck as much - it's good for some views. Cocoa/Objective-C are so well designed that I have been struggling with an impedance mismatch when going back to Java/Flex and most importantly, Windows and 'Not Responding'. I can understand why Unity3D and MonoTouch.Net make things easier for developers. Because at the abstract level, the consumer doesn't care how you wrote the application - they care about how your app makes them feel - as in did they get personal value, does it make them look cool, does it look kick-ass...However, if an app can be written once in a framework and deployed to Android and iPhone simultaneously, that weakens the main tent pole of Apple's strategy.I don't support Section 3.3.1, and I believe it will be enforced (with high-profile exclusions).