Adobe's Mike Chambers put up yet another screed against Apple and their iPhone platform -- specifically the disallowing of cross-compilers -- this time basically saying Adobe was going to stop work on Flash CS5's iPhone packager:

The primary goal of Flash has always been to enable cross browser, platform and device development. The cool web game that you build can easily be targeted and deployed to multiple platforms and devices. However, this is the exact opposite of what Apple wants. They want to tie developers down to their platform, and restrict their options to make it difficult for developers to target other platforms.

Adobe, of course, doesn't care about devices because they don't make devices. They make content development tools (CS5) and delivery platforms (Flash), and as much as they decry Apple wanting to "tie developers down to their platform", that's exactly what Adobe wants as well -- they just want the tied down platform to be Flash.

Apple's Trudy Miller responded to CNET:

"Someone has it backwards--it is HTML5, CSS, JavaScript, and H.264 (all supported by the iPhone and iPad) that are open and standard, while Adobe's Flash is closed and proprietary," said spokeswoman Trudy Miller in a statement.

No doubt both companies are doing what they feel is best for their platform. Adobe makes things easier for developers and more plentiful for users, while Apple wants developers to make more purposeful apps that are better for their devices and users. Arguments can and have been made for both approaches. For Adobe to pretend they're any nobler in these arguments, for them to use faux-nobility to try and rally developer and user support, however, is more than a little disingenuous.

Either way, Adobe seems to be throwing in the Apple towel and going all-in on Android, which is how they really should be handling this -- on the technological battlefield by getting great Flash apps made.

Otherwise we'll say it again -- it reminds us of Microsoft when Firefox shook up the browser space after years of IE6 complacency and ActiveX lock-in. If nothing else, HTML5 might just get Flash going again, though if their as slow to respond as Microsoft has been getting IE9 to market, it might be too late.