And there are ways to manage that which don't involve dictating what software developers can and cannot use to create iPhone apps. Apple didn't choose to restrict apps based on power draw, or efficiency, or anything like that--instead, they deliberately targeted another company's development software.

And the reason it's bad is that it limits development. You can, under these rules, either develop for the iPhone or develop cross-platform apps.

It's worth pointing out that Adobe isn't bringing claims against Apple, so far as I know (at least, any claims they're bringing aren't what's being discussed, here). This is the FTC and the DOJ making inquiries.

The FTC (DoJ lost the battle to pursue AAPL) is not after apple because of Flash. Rather it is AAPL's pattern of conduct including Flash,

You are 100% correct about the writing of s/w and I was wrong. I had relied upon my memory and should have spent five minutes fact checking myself. It was AAPL restricting their OS to their own hardware while M$ would let their shit run on any manufactures h/w that resulted in the current market numbers.

Again as long as a privately developed API works, does not cause h/w crashes, or compromise security AAPL's insistence on using propitiatory tools will hurt them.

FWIW IMO the only issues that will stick is around advertising and music downloads. Flash will shown to be a resource pig and after awhile the FTC will accept the claim. Development tools is a tossup but I would bet that the FTC will likely drop the matter (if anything comes of the claim it will come from Europe.)

They did not deliberately target Adobe. They deliberately targeted meta-development environments, and not only Adobe's, but also MonoTouch. Sure, maybe, these issues can maybe be addressed. However, we're talking about developing apps using code hand-written native versus code being generated by a third-party platform.

It's quality over quantity. Their hand-developed code will almost always result in a higher quality application than the generated code.

Yeah, it limits development. However, if it is bad or not is in the eye of the beholder. If what Adobe's Flash did to the web was good, then I want to be bad. However, let's not let act like Apple is making developers choose their proprietary tools over Adobe's. It's Objective C code being compiled by GCC. Neither of these things are proprietary.

You want to develop cross-platform for the iPhone and other mobile devices. Use HTML/CCS/JavaScript. It's probably much more efficient than what CS5 would create anyways.

Adobe made an complaint to the FTC regarding Bloomberg

Certainly there are many reasons to criticize Apple: iAds, the App Store, censorship, DRM, labor,etc... I'm not a fanboy (I use Arch Linux, though I do have an iPhone). The Adobe vs. Apple is, I believe, not a valid reason. Apple should have every right to keep Adobe's proprietary software off of their devices. It's all about technical reasons, not corporate warfare.

That's really a technicality. The rhetoric is about Adobe, the new TOS came out in response to a planned Adobe product--it's quite clear that Apple aimed this at Adobe, and that anyone else who happened to get hit was just a bonus. There is no reason to limit the means of production, here. You say cross-platform apps will always be worse, I say they'll be worse until either someone develops a better third-party platform, or (more likely) the hardware advances to the point where such limitations can be dismissed.

This is very much about corporate warfare; the technical reasons are secondary. If technical reasons were the real impetus, then Apple would have put technical limitations on app development. Instead, they put corporate limits on app development.

No way, Apple and/or Microsoft and/or Windows is in litigation.......again?

I disagree for reasons I've previously stated, and at this point, I don't believe I'm going to change your mind, nor you change mine. Fair enough. I'll just ask, what do you think Apple has to gain by denying Adobe products to generate iOS applications? Keep in mind that the iOS SDK is free, including the development environment, and developers that would use Adobe's CS5 to develop iOS applications would still have to pay Apple the $100 charge to become a ADC member.

Apple gains a few things. The first is pretty simple: they can get more iTunes customers by freezing out Flash. If an iOS user wants to watch a video or play a game, they'll most likely have to get it from the iTunes store. They won't have access to services like Hulu--heck, at this rate, it's looking like they won't even have access to YouTube.

The second is less straightforward. By preventing developers from creating cross-platform software that works on iOS, Apple is making a bid for a much larger market share in mobile devices. Developers will have to make a choice: will they develop software for iOS, or will they develop software for other platforms? They can't reasonably do both. Apple is betting that the popularity of their products will entice developers to focus on iOS apps, and their rules mean that developers who do so will do so to the detriment of all other mobile devices.

There's nothing wrong with that strategy in and of itself, of course; trying to make your hardware more popular by enticing more developers is the name of the game. It's the way Apple is 'enticing' developers that's the problem.

To be sure, Adobe's no better. They've got a deathgrip on Internet multimedia, and part of me is cheering Apple on for working to pry Adobe loose. And it is important to wean the Internet off of its Flash addiction. Especially web designers. One more goddamn Flash website intro, I swear to god...

Anyway. We'll see what the FTC says in a few months years decades.