Earlier quoted context omitted.
JavaScript (in mobile webkits) also implements touch events, while Flash doesn't.
^ Lies: http://www.adobe.ca/devnet/flash/articles/multitouch_gesture...
Thoughts on Flash
171–180 of 522 posts
Re: Thoughts on Flash
#172> For example, although Mac OS X has been shipping for almost 10 years now, Adobe just adopted it fully (Cocoa) two weeks ago when they shipped CS5. right. And the Finder - a piece of Software central to OSX was using Carbon until... when exactly? At most 6 months prior to when CS5 came out. iTunes - a corner stone of the iPhone software world? Still on Carbon. If I hate one thing, it's hypocrisy. Aside of that, nice…
Apple purposefully wrote Finder in clean Carbon as an example to developers, to prove that it was possible to make good cross-platform software. iTunes was also written very carefully -- and very cleanly -- in Carbon to be cross-platform. Adobe, however, hacked Creative Suite into Carbon with buggy, inefficient code and then took 10 years -- ten years -- to schedule the time to fix it.
Re: Thoughts on Flash
#173Otherwise, I was with it until the justification for the new clause. That justification just doesn't hold up. Developers are not going to sit around and wait for Adobe to implement a feature they need; they will do as they have done now, and implement it themselves as necessary. The justification is very lame imo.
Re: Thoughts on Flash
#174The most brilliant part of Apple's marketing here is leveraging infighting and unintended consequences in the free software community. They don't care about open standards - that they would is, on the face of it, absurd. What they do know is that they will evoke much support for championing JS/HTML/CSS as an open plaform, and that it poses no actual threat to their App Store control. This is because of two reasons: F…
The most succinct explanation yet - pity your post is one of the view voices of reason in this thread.
Re: Thoughts on Flash
#175I love this. Apple clearly laid out their reasoning, using facts and persuasive argument. The world needs more of this. Obviously, there is some spin in the post, and I don't completely agree with 100% of it, but I love the level of discourse.
I have trouble swallowing some of this. A few of these theories have been debunked successfully. I have a small problem with this "don't look at the man behind the curtain" routine. Proprietary is proprietary. Don't try and swing it. Battery Life: http://vimeo.com/9705969 , http://vimeo.com/9724682 Delays: http://www.neowin.net/news/adobe-quotapple-hurts-customers-f... Touch/Scroll: http://www.mikechambers.com/blog/2…
Re: Thoughts on Flash
#176We techies are guilty of always wanting everything. I see projects a lot of time, that won't move forward because the developers will not have the balls to stand up and draw the line between things the software will to, and the software will not do. It's just more comfortable to avoid confrontation. When I read this, I felt that Steve really knows what he wants, and in order to get it, he is willing to eliminate thin…
I swear, I used to think the reality distortion field was a dumb metaphor...
Re: Thoughts on Flash
#177Earlier quoted context omitted.
Which arguments are FUD?
* Flash websites will have to be rewritten because it relies on 'rollovers', which is not part of Apple's 'revolutionary' touch interface: overblown for two reasons - a) few stuff will have to be rewritten (many videos show desktop Flash content working on mobile phones without a problem); and b) this is not a problem with Flash, as any JS/HTML-based interface that relies on rollovers has the same issues. * Flash is…
We should not NEED flash for reproducing video on the Web, no matter what codec or platform are involved.
Re: Thoughts on Flash
#178Earlier quoted context omitted.
Yes, it's stupid. But with Apple, I feel I only need to fear their intention, not their wording. The intent here, it seems to me, is to stop Adobe from making crappy commercial middleware for Apple's platforms. The wording is overly broad and stupid, but I'm no longer as afraid of it. If they were intent on getting rid of everything under the sun that isn't straight C, Obj-C or C++, there would already be an App-ocal…
The intent here, it seems to me, is to stop Adobe from making crappy commercial middleware for Apple's platforms. This is actually the biggest part of Job's argument that I don't buy. If their intent was actually to stop crap from being produced, they would just reject apps that are crap from the App Store as they do now.
Still, 3.3.1 is poorly worded, so it's not a great solution.
Re: Thoughts on Flash
#179Flash is closed, Apple is open. Huh? I can build a flash app entirely for free, legally, with zero restrictions, forever, on the tools I used to write it, or where I can deploy it to. Adobe has bent over backwards to make players (also free) backwards compatible. That's pretty open. I must pay to build an iphone app, which I can only do on a computer owned by the same company, running an OS owned by the same company.…
Apple makes Bill Gates look like Richard Stallman? Let me ask you something. How many of Microsoft's competitors are building products that compete directly with Microsoft core offerings using the source code to Internet Explorer?
Re: Thoughts on Flash
#180And here we can find the real locus of the dispute: "...although Mac OS X has been shipping for almost 10 years now, Adobe just adopted it fully (Cocoa) two weeks ago when they shipped CS5." If Adobe didn't drag their feet for so long on the CS products, I think the other reasons wouldn't have mattered as much.