Adobe Not Worried About the Future of Flash
An anonymous reader writes "Adobe company man John Dowdell isn't worried about the future of Flash. He writes in his company blog, 'There's really no "HTML vs Flash" war. There are sure people inciting to create such a war, and individual developers may have strong practical reasons to choose one technology over another, but at corporate levels that drive strategy, all delivery channels are important Adobe territory, whether SWF or HTML or video or documents or paper or ebook or e-mag or film or packaging or whatever. Adobe profits by making it easier for creatives to reach their audiences. We're on the verge of a disruptive change that, I think, will dwarf that of the World Wide Web fifteen years ago. It was great back then when any wealthy person with a workstation in a wired environment could easily reach any creative's webpage. With these cheaper devices we'll be reaching far more people, and with pocket devices we'll be reaching them throughout the day instead of just when "logged-on." The WWW was merely a pale precursor of the excitement we're going to see, I think.' It's interesting to note that he talks about the World Wide Web in the past tense. I find it instructive as to Adobe's perspective. Personally, I'm not worried about the future of Flash either. I don't think it has one."
Personally, I'm not worried about the future of Flash either. I don't think it has one.
Except that it's pain in the ass to create Flash-like games with HTML5. You have to use all kinds of hacks to accomplish that, while designers and Flash game creators are familiar and love Flash authoring tools.
Flash isn't just about video, even if it's the most talked part of it here on slashdot.
It'll take a while, because IE 9 doesn't support XP, but it'll happen. Flash dies once XP dies.
Microsoft would like to fully control the interfaces, but when they fail at that they'd at least like to stop any other company from controlling the interfaces. Microsoft will settle for open standards as required to kill things like flash.
We can thank Adobe for IE 9 getting SVG and HTML 5 video support.
Like there is to block flash.
I do not want any video type stream to load when i am going to a web page until I have made the decision to watch it.
That is not an anti flash statement because I do make the choice to watch a lot of flash. But it is at my discretion and not the web page designers.
If it wasn't for flash block, I would spend all day waiting for news sites to load instead of actually reading the news. I hardly ever watch the flash on those types of sites, and they are probably the worse offenders of loading up the crap flash. Now other sites, which by the nature of the site presents its content via flash. yes, I do watch it. But, only after I have clicked the specific flash object I want.
Anonymous comments are as pathetic as the anonymous "sources" that contaminate gutless journalism from the New York Time
When you really look at it, there's no reason that Adobe shouldn't embrace HTML 5. Fundamentally, maintaining a cross-platform plug-in is not a profit center for them, it's a cost. They don't make money on the plug-ins, they make money on the Creative Suite product which allows designers to create animations, games, and the like easily. All this work of maintaining their own actionscript standards and standard library just serves to make their pay products more useful.
Imagine for a moment that at some time in the near future, Adobe has a new option on the menu "Export to HTML5". Would this make their product less useful? Of course not. Widespread adoption of HTML 5 means that their product can now be used to create content for even more devices, including several, like the iPhone, from which they have previously been locked out. And it wouldn't even be surprising if over time they transitioned entirely to HTML 5, giving up the work involved in maintaining Flash. They probably won't do this in the short run, but in the long run, it's entirely plausible.
I'm sure some people will point out that the move to HTML 5 opens them up to more competitors, and it does. But they've already got competitors even with the Flash ecosystem. There are a variety of ways to make swfs, including swftools, FlashDevelop, and the free Actionscript compiler which Adobe itself released as part of the Flex SDK. There are even a few other pay products out there. So, essentially, they already are in a market where there are a bunch of other tools which are cheaper but either can't produce complex content or require a bunch of coding to produce similar content. If they switch over to HTML5, they will likely be in the same boat, just in a bigger lake. Sure they'll be competing with DreamWeaver or whoever, but they'll have a clear and immediate advantage when it comes to "Flash-like" stuff such as animations and games.
So in summary, if they manage the transition properly, moving towards HTML5 means less costs and a bigger market. That sounds to me like a pretty clear win.
I couldn't care less what new gizmos and glitz the web has ... what I care about is that if I create apps, just like documents and databases, I want to still be able to access and use them 20 or 40 years from now without recoding and reformatting them. The gold rush is over. What I want now is bulletproof base of archival-quality standards, not ones that reinvent themselves every product cycle.