Wednesday, April 14, 2010

Sorry, Adobe, you screwed yourself « Sharing the truth one thread at a time

I realize this is a pro-Mac, pro-Apple forum. But being a designer myself, and an iPhone owner, I feel this decision by Apple is really just hurting the developers and designers. If I want to create some cool game for iPhone, I need to learn Objective-C? Common.

And what you don’t know or hear from the Apple propaganda machine is that Apple is not fixing the bugs in their own s/w that is preventing Flash from improving cpu usage on Mac by taking advantage of h/w acceleration for video decode. The comparisons to HTML5 are bogus because you’re comparing apples (pardon the pun) to oranges. A comparable comparison by a 3rd party (I think I saw this article on streamingmedia.com) where HTML5 compared to Flash with gpu support was the same. The performance problems that everyone keeps talking about is mainly due to having to do all the heavy video decoding in s/w vs. h/w.

Also, Apple is pushing HTML5 on everyone. But their own browser, Safari, on Windows doesn’t support H264. So how are they really be seriously pushing HTML5 as the standard for people to adopt? They’re still forcing people to have 2 versions of their site; one for iPhone/iPad, and one for everything else. Sure there may be some people willing to do that now to get on the iPad. But Apple went down this path before with a closed environment, and it got Steve booted out before he came back to bring them to the promise land.

I have total respect for the company. They make great products. And I totally respect their business motives here. But Jobs is not being honest about his motives. All this Flash bashing is just a smoke screen to stir up anti-Adobe/anti-Flash sentiment, so people don’t talk about the real issues, or motivation.

Did you know that of the bugs Adobe filed that would allow them to do h/w acceleration, not one of them got fixed?

Jobs claims that this translation layer results in subpar apps. What a crock of shit. You don’t think people can write crappy apps in Objective-C? Apple screen all the apps anyway. If they’re serious about their quality claims, why don’t they screen for quality, or have some set of tests that an app needs to meet to be deemed high enough quality to make it on their platform. In the end, Adobe’s packager is just translating swf byte code to native code, just like any Objective-C program compiles to. What’s the difference? But again, Jobs is deflecting all that with these ridiculous claims. Just be honest, and live or die by your decision.

     by mc April 11, 2010 at 9:35 pm

Posted via web from Rob's posterous

No comments: