Interesting. Stakeholders will want to see "risk factors" mitigated as much as possible...I wonder if Adobe is going to go to Apple and beg and plead, or start supporting a competitor heavily (Android?).
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.
I smell yet another lawsuit brewing...
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.
I'd be willing to be if Adobe could port Flash using native Cocoa it would be allowed.
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.
I honestly wish Apple would cooperate with Adobe and bring flash to the iPhone/ iPod touch/ iPad. I know the fanboy's will flame me for this one, but I honestly think Apple is too damn controlling sometimes.
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 I were Adobe I'd announce that CS5 will be the last Mac release. I'm betting Apple might be persuaded to change the stance on Flash.
Personally I think Flash blows on any platform, but Apple's stance on this seems extreme at times.
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.
The only complaint on flash is cpu usage, other than that it's great!
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.
The least Apple could do is let flash run on their hand held devices UNTIL HTML5 has been adopted by nearly everyone. At least there wouldn't be any inconvenience to anyone in the mean time. Although, Apple could care less about inconveniencing their consumers, it seems.
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.
"...the company released a modified developer licensing agreement that appears to prohibit the use of a feature in Adobe's forthcoming Flash Professional CS5 to export Flash content into the native iPhone format."
Now that is quite a jerk move on Apple's part if that's true....
Really now? You can't be serious!
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
I understand where Apple is coming from.
However, by heavy-handing developer guidelines, I worry Jobs is risking isolating the company from the rest of the world. This didn't work well in the 90's and it won't work well in the coming decade.
Why? This seems absurd right now because the app store is the shizzle today. However, every other company in the world is working together (with Adobe on open screen project) and while such a big force takes time to gain speed, it's going to steamroll over Apple in the next year or two (three at most).
Why are customers going to pay the Apple tax, when other smart phones have more features, less restrictions, and more prevalent in the market place? Why will developers put up with Apple's draconian guidelines when Android is taking over the world.
Google/Android is the Microsoft of the coming decade. If Apple locks itself up in the walled garden, don't expect the iPhone success to be long term. What's that saying about history?....
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).
I don't understand the Flash hate here.
My macs always handle flash like crap and overheat and consume tons of CPU, but I was always under the impression this was more due to Apple than to Adobe and some weird restrictions on what the client can do.
I have much weaker PCs that handle flash with no problem, so at least past the Intel move, I would have to assume that the problem is with the Mac client.
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?
Now we see the *real* reason that Apple hates Flash so much. They don't want anyone using Flash - instead of Xcode - to develop iTouch apps. This issue has always been at the heart of the Flash boycott.
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.
Personally, I dislike Flash and I'm happy to see it go. It's buggy and bloated and its time has come and gone. Even if Adobe ships Flash CS5 with the ability to compile iTouch apps, Apple will never allow them into the store.
I applaud Apple's desire to advance open standards and break the stranglehold that certain proprietary plugins have over the web experience. The web is about being open, not locking users into a proprietary format.
Hate on Apple all you want, but they've done a lot more than Microsoft, Adobe, etc. to advance an open, standards-compliant web experience. WebKit is pretty awesome, so awesome that even Google uses it.
Plugins need to go. Users shouldn't have to worry about if this or that plugin is installed, if it's up to date, etc.
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.
Run Windows on your Mac and Flash will not drain your battery anymore than html5 with h.264. This all comes down to Apple not giving Adobe access to APIs to utilize h.264 with Flash.
The only reason Flash seems like a resource hog is because we're running it on a Mac. My octo-core Mac Pro with 18 gigs of RAM can't handle even the simplest flash games......... Meanwhile my 5 year old HP laptop, running Windows XP does just fine.
This tells me that it's
Apple that is lazy and unwilling to fix problems on their end which cause Flash to crash systems.
As a user I can care less if Flash isn't real code. I just want the web to work properly on my computer and other devices. As it now stands I can't access certain websites because Apple won't allow it, even though they say I have the entire web in my pocket
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?
resource hog? ever look at what itunes rings up when its loaded? Me thinks that jobs is starting down a slippery slope. i would say the majority of the iphone users couldn't care less about flash as they just want their "websites" to work
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.
It wouldn't. Mac users are less then 10% of total user base worldwide.
And 50% of Adobe's sales of key products.
Clearly Apple's intent is to stop the mass generation of 'knock-off' applications. Even a translator that converts into c/c++/obj-c is against the rules because it is against Apple intent..
No, Apple's intent is clearly to provide an efficient, reliable, secure system - all of which are inconsistent with using Flash.
I would say with 98% of Internet acceptance (devices capable of displaying Flash content) as of last year, IT IS AN ACCEPTED STANDARD, whether SIR Stevie likes it or not.
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.
