Will Adobe Sue Apple Over Flash?

An anonymous reader writes "Apple's iron-bound determination to keep Adobe Flash out of any iWhatever device is about to blow up in Apple's face. Sources close to Adobe tell me that Adobe will be suing Apple within a few weeks."

Comments

I'm conflicted

[ShadowRangerRIT]

In a battle between two vendors, one with a closed source, insecurt framework and the other with a closed platform, which side do I root for?

..and as I said on a previous thread.

[jcr]

Louis Gerbarg has written up a very good explanation of the issues involved.

Quote:

Adobe is a large company with a significant, and complicated, relationship with Apple. They have frequent high level contacts and meetings. Adobe has known for quite some time about Apple's desire not to have Flash on the iPhone. There is no doubt in my mind that if they asked Apple to bless this they were rebuffed, and if they didn't ask the only reason they didn't was because they knew Apple would say no. In either event, they announced the product to their customers and sold them on an idea they were not in a position to deliver, hoping Apple would be unwilling to piss off developers by not fulfilling Adobe's promises. They tried to force Apple's hand by putting Apple in a position where in order stop the Flash they would have to do it publicly in front of Adobe's users. That was a bad call on Adobe's part.

Read the whole thing.

-jcr

TFA wasn't clear

[mcgrew]

What grounds are they suing under? Breach of contract? Why should Apple be forced to use Adobe's stuff if they don't want to?

Re:TFA wasn't clear

[Anonymous Coward]

The short version: Apple is telling developers that they can't buy Adobe *tools* to produce *native* Apple-platform applications.

The long version:

1. Adobe Flash is buggy and crashes a lot. Steve Jobs also seems to have a personal beef with it for some reason.
2. Apple says, "No flash on our iAnything platforms."
3. Adobe says, "Please?"
4. Apple says, "No!"
5. Adobe says, "Okay, we've made a compiler that takes a Flash script and compiles it to an iAnything native application, using HTML 5, Apple's C-variant, and Apple's API."
6. Apple says, "We've added a clause to our developer contract that says that developers are not allowed to use anything that translates code from one language to another for the iAnything platform. You have to use OUR tools, and you must write in OUR language from the start, or you - the developer - cannot play with us."
7. Adobe says, "..."

Got to side with Apple on this one...

[rimcrazy]

They have a platform worth billions. Tens of billions. They have chosen to make it closed. You as a consumer can chose to use there platform or not, that is up to you. For them, to potentially put the fate of a multi-billion dollar product in the potential hands of a company that makes development content for this multi-billion dollar platform and not control it is suicide.

You can argue the merits of closed or open but in this case the point is moot. iPhone is closed and Apple wants it that way. They are not going to put their fate in the hands of Adobe. The only legs Adobe may have to stand on is if they were lead to believe that their platform was to be accepted (written contract or verbal) and then at the 11th hour to be shafted? Well then maybe they have a case.

Hey, I was the engineering dept. manager back at VLSI Tech back when chip sets was a good business. Intel decided, rightly so, that they could not put the fate of their CPU's in the hands of 3rd party chip set vendors. In ONE product cycle (after they finally figured out how to make them) they took 90% of the PC market with their chip sets. Did it hurt? Yea, it hurt. We went from $250M/yr to $25M/yr in 12 months. I lost my job along with a host of others. That being said, I still can't fault Intel for what they did. Quite frankly I'm surprised it took them as long as it did. The case in point with Apple and Adobe is no different.