Supporting a competitor won't help them (but even if they try, 10.1 for Android is late and testers so far say it's still a resource hog. Not to mention that it's limited and isn't a full Flash implementation, anyway.) And there's the fact that other platforms (can you say Windows Mobile 7) don't support it, either.. If developers have to write a different version for mobile 10.1 apps, they might as well write a proper html version.
Based on what? I wish people would stop making inane comments based on nothing more than their own delusions. And don't try 'antitrust'. It doesn't apply because Apple doesn't have a monopoly.
That's possible. If they wrote a decent version of Flash, Apple would undoubtedly consider it - even though it would still violate the SDK terms.
Why don't you tell us what part of the Flash code was written by Apple? Flash is allowed on Macs - and it sucks badly. That's Adobe's fault, not Apple's. I have a Core 2 Duo 2.3 GHz, 4 GB MacBook Pro. Flash shoots the CPU to over 100% - and the fans come on within seconds. If it takes that much CPU power, how in the world do you expect an iPhone to handle it?
If Flash blows, why would you want to see it continued? Apple is pushing for good quality apps - it seems to me that you should be supporting that if you think Flash stinks.
As for making CS5 the last version for Macs, that would be an insanely stupid thing to do. Half of their revenues on most apps comes from Macs. Not to mention that it would simply encourage Apple to write their own pro image editing app - which would undoubtedly be better than Photoshop.
Well, CPU usage, security (one of the biggest security holes out there), performance, stability (top source of crashes on Macs according to Apple - and my experience supports this). Other than that, it's great.
That would be insanely stupid. If Apple allowed Flash, then lazy developers would simply continue to use it. HTML 5 would never be adopted. PLUS, every time a Flash app caused your phone to slow to a crawl, drained the battery or caused a crash, users would blame Apple, not Adobe.
Maybe you should read both sides of the story before passing judgment. The other side is that this type of environment was never allowed in the SDK and Adobe thought they could work around Apple's rules. Apple simply clarified the rules that have always been there.
How about reading what a Flash developer has to say:
http://www.bit-101.com/blog/?p=2410&cpage=2#comment-509066
Oh, yeah. No one is ever going to develop for the App Store. Those 185,000 applications all wrote themselves.
Android has some potential - they added something like 15,000 apps in the first part of this year. Unfortunately, Apple added 85,000 in the same time period. AND that's even after Apple threw out about 20,000 junk applications (many of which are now on the Android store).
At least SOME of the problem is with the Mac client (although there are plenty of Flash performance and security problems on Windows, as well). But even if what you say is true, who wrote the Mac Flash plugin? Do you think Apple wrote even a single line of code? As for restrictions, that's nonsense. Adobe has access to the same APIs that everyone else has. Other applications work just fine on Macs. Heck, even Microsoft is now writing decent (still not great, but decent) Mac software. Why is it Apple's fault that Adobe can't be bothered?
Not according to Apple's public statements. It's about performance, security, and stability. And, in the case of the Flash to iPhone compiler, ability to support Apple's new features.
And that's really the bottom line. Flash serves not useful purpose that isn't served better by an open standard which doesn't bring your computer to a screeching halt or infect your system with malware.
BS. Specifically which APIs does everyone else have that Adobe doesn't? There are plenty of other apps that work just fine on Macs. What makes you think Adobe is the only one who doesn't have access to Apple's APIs?
And why should Apple be forced to fix Adobe's worthless code? Adobe has had years to fix it and has done nothing. The writing was on the wall 3 years ago with the introduction of the iPhone - yet Flash doesn't run one whit better today than it did then. Why is it Apple's fault that Adobe has simply ignored the problem for years?
Seems to me that you're more interested in making thing up than dealing with facts.
iTunes uses 11% of one CPU on my Mac. Flash uses 115% - even when it's not doing anything but displaying a page with some Flash menus.
And 50% of Adobe's sales of key products.
No, Apple's intent is clearly to provide an efficient, reliable, secure system - all of which are inconsistent with using Flash.
It is something of a de facto standard on destkops and laptops - but Apple has done nothing to block it there.
It is NOT a standard of any type (open OR de facto) on mobile devices. In fact, there is still not a full Flash implementation running on ANY mobile device that I know of. Even Flash 10.1 (which isn't out and still has performance problems) won't support your argument both because it only runs on Android and because it is a limited subset of the Flash 'standard'.
Far better to drop it know and go to an accepted standard that works on all platforms.
