As somebody said in another post, Flash great distribution it's because it was something that designers could do with little programming (if not none at all). What Adobe should really focus is to create a valid equivalent for HTML5 and try to become the standard editor for HTML5 for all those people who don't know how to code.
Adobe Responds to Jobs
111–120 of 128 posts
Re: Adobe Responds to Jobs
#112Earlier quoted context omitted.
> Jobs is trying to undermine the competition because he fears that he made the wrong choice. You think so? Smart-phones have been around a long time. The iPhone was announced over three years ago, yet here we are in the middle of 2010 and mobile Flash is still nowhere to be found on any mobile device. How is that not Adobe's fault? Is Adobe just not very interested in mobile Flash, or are there very serious technica…
Others have already pointed out the N900. On a more historical note, mobile Flash did exist in 2007. I was using it to watch Youtube on my Nokia N800. It was slow -- the device didn't have enough CPU power to simultaneously download and playback, so you had to pause the video and let it cache completely first. But it most definitely did exist, and I am convinced that implementation would have worked well on 2009 hard…
Performance of Flash on the N770 was pretty bad but I have a feeling that the 252Mhz OMAP and 64MB of RAM were the problem.
I bet the 1Ghz Snapdragon/512MB RAM combo you're seeing in new HTC devices could run Flash fine if the Nokia Maemo devices could chug along.
Re: Adobe Responds to Jobs
#113Earlier quoted context omitted.
Well see even there it's Job's contention that crossplatform frameworks should have displaced native frameworks and limited the hardware manufacturers to effectively just supporting the crossplatform frameworks. Surely the best argument against Job's position is the iPhone itself. The most important and dominant crossplatform framework in the world is HTML+JS and Apple actually wanted it to take the place of native f…
> Surely the best argument against Job's position is the iPhone itself. The most important and dominant crossplatform framework in the world is HTML+JS and Apple actually wanted it to take the place of native frameworks. But we all know how that ended and now we have the App Store. And with this paragraph you exactly proved why Flash doesn't have sense on the iPhone.
I don't get what you mean.
Re: Adobe Responds to Jobs
#114Earlier quoted context omitted.
>My desktop CPU bought in 2000 used 30 W. And didn't it support Flash? >Now I can come to a lot of web pages where only Flash ads use 100% of a modern CPU! Okay, so show a placeholder for Flash content and only load and play the things the user double taps.
Running flash content on a PC bought around 2003 is actually pretty choppy. I installed Windows 7 on an old Athlon 1.6 ghz machine a month ago and tried to watch youtube with it -- the videos looked like they were going around 8 fps. I can watch old divx movies on it, but I can't watch youtube full screen... it's pretty sad. This machine was fast enough to play Quake 3 and a dozen other gaming titles, but is too slow…
Newer Flash Videos codecs like H.264 probably are that intensive. Codecs have changed over the years, giving us better quality, but also requiring hardware support or lots of go juice to run well.
Re: Adobe Responds to Jobs
#115Apple v. Adobe is like watching two drunk bus drivers take to the streets. You don't just want off the bus, you want off the road.
Re: Adobe Responds to Jobs
#116Earlier quoted context omitted.
i disagree. they ignored all the main points in apple's argument. a "This is why Flash is worthwhile" response is better than a "Well, at least we'll be on android."
I disagree... Apple's argument is really poor and arguing against it would be difficult for this reason, any thorough response would probably look defamatory. Its a lot easier to just treat it with the contempt it deserves. For example, it contains intrinsically weak arguments. e.g. the section headed "Fifth, there's Touch" is equally applicable to HTML5 and infact most of the rest of the internet technologies. If yo…
I was talking to one of my professors that teaches Flash/ActionScript at the University I just graduated from yesterday, and the main issue at hand is that Adobe in Flash still does not have a good way to handle touch events, nor is there any way to use ActionScript to add any touch events. Flash is dropping the ball in that regard.
Re: Adobe Responds to Jobs
#117Adobe is basically saying that Flash will be available on competitor's phones and the market will decide; which is exactly the right response. I wish most tech bloggers would take this view and just shut up with the endless "analysis" of Flash and Apple. Flamewars don't decide anything, the market does.
>Adobe is basically saying that Flash will be available on competitor's phones and the market will decide; which is exactly the right response. Perhaps not. http://www.engadget.com/2010/04/29/adobes-ceo-jobs-flash-let... "There's no official transcript yet, but the Wall Street Journal just live-blogged an interview with Adobe CEO Shantanu Narayen, in which he responded to the Steve Jobs "Thoughts on Flash" letter pos…
So Flash crashing on my Mac is because of the Mac OS X operating system when those same crashes happen under Linux as well, but not under Windows? Methinks it is more a case of shoddy engineering.
Re: Adobe Responds to Jobs
#118Earlier quoted context omitted.
Others have already pointed out the N900. On a more historical note, mobile Flash did exist in 2007. I was using it to watch Youtube on my Nokia N800. It was slow -- the device didn't have enough CPU power to simultaneously download and playback, so you had to pause the video and let it cache completely first. But it most definitely did exist, and I am convinced that implementation would have worked well on 2009 hard…
Simply existing is not good enough for Apple, their bar is higher than that. See copy/paste on iPhone for an example: They could have implemented the menu-driven kind of copy/paste found on Palm Pre and Android, but they wouldn't because it sucks. Apple prefers nothing at all over a solution that sucks. So we got nothing in place of cut/paste, until they figured out to do it in a way that didn't suck. Simply existing…
You are, of course, correct; I was responding to my parent's unqualified claims that "mobile Flash is still nowhere to be found on any mobile device" and "mobile Flash didn't exist in 2007".
Re: Adobe Responds to Jobs
#119Earlier quoted context omitted.
I disagree... Apple's argument is really poor and arguing against it would be difficult for this reason, any thorough response would probably look defamatory. Its a lot easier to just treat it with the contempt it deserves. For example, it contains intrinsically weak arguments. e.g. the section headed "Fifth, there's Touch" is equally applicable to HTML5 and infact most of the rest of the internet technologies. If yo…
I was talking to one of my professors that teaches Flash/ActionScript at the University I just graduated from yesterday, and the main issue at hand is that Adobe in Flash still does not have a good way to handle touch events, nor is there any way to use ActionScript to add any touch events. Flash is dropping the ball in that regard.
Flash 10.1 handles multitouch events:
http://help.adobe.com/en_US/FlashPlatform/beta/reference/act...
Re: Adobe Responds to Jobs
#120Adobe is basically saying that Flash will be available on competitor's phones and the market will decide; which is exactly the right response. I wish most tech bloggers would take this view and just shut up with the endless "analysis" of Flash and Apple. Flamewars don't decide anything, the market does.
Yeah this was a clearly worded and classy response, definitely better than I expected.
They said about as much as they could, which isn't much. Jobs didn't exactly leave them any wiggle room.