Comments on: The Apple is Really Rotten

By: Blue

Blue — Fri, 30 Apr 2010 11:31:21 +0000

I think the question is not what Adobe should do, but rather what Apple users being Adobe users at the same time should do – and I think they are HUUGE. There is an intersting Open letter to Steve Jobs:

http://applesorangepress.wordpress.com/2010/04/30/open-letter-to-mr-jobs/

Maybe this is just the beginning.

By: Bob Taylor

Bob Taylor — Wed, 28 Apr 2010 14:35:46 +0000

It makes me chuckle when I read comments like that. A tools a tool, and Flash is an extremely useful one. You can slander it all you like, but numbers are what counts, not the prattle of some minor developer having a “I’m right and you’re wrong” hissy fit

By: sEAN.

sEAN. — Wed, 28 Apr 2010 14:23:40 +0000

I’ve had to use Adobe products for the last decade. A happy day in my career was when I switched to Apple. Audition is ASS. Premier is ASS. Dreamweaver is is a joke. And the world can totally live without Flash.

I’m reading all this whining about how evil Apple is…

If Apple was a automobile manufacturer and Flash made carburetors, no one would blame Apple for putting fuel injectors in their cars instead of carbs. The people at the Flash Carburetor Factory would probably be bummed. I’d like to think they would whine about it as much has Adobe has.

By: Guilhem Ensuque

Guilhem Ensuque — Wed, 21 Apr 2010 14:46:49 +0000

> [Adobe should] make their packager compatible
> with the new policies by showing that the work flow
> includes a source code conversion from AS3
> to one of the approved languages before compilation

This is exactly what we do at OpenPlug: ELIPS Studio does generate C++ from AS3. Still, as some other commenters have said here, it remains to be seen whether this is enough for Apple. (full story here: http://developer.openplug.com/index.php/blog/187-update-apple-331-elips)

What should Adobe do next ?

Well here’s my take :
1- open source the flash player to quell critics and share the evolution costs in an open way
2- get involved in HTML5 implementations (e.g. webkit)
3- focus on tools: Make Dreamweaver spit out HTML5/CSS3/JS for mobile web apps
4- focus on tools: idem for Catalyst
5- focus on tools: idem for Flash/Flex Builder + with native mappings for the unique features of each mobile platform
6- Buy Palm (half kidding, just consider how all the others bundle their apps platform with mobile hardware: Microsoft / WindowsPhone7 phones, Google / NexusOne, Apple / iPhone)

Further detailed in this blog article: http://www.visionmobile.com/blog/2010/03/why-adobe-should-change-its-mobile-strategy-again/

By: Sasa

Sasa — Thu, 15 Apr 2010 05:30:40 +0000

They will loose more than they gain if they pull their support from osx.
after all who uses chrome except the very few among designers!
Better if they find a way to work together for the benefit of all.