Slashdot Mirror


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."

4 of 328 comments (clear)

  1. SVG+video in IE 9 is the death blow by r00t · · Score: 5, Interesting

    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.

  2. archival quality Internet, please by Fractal+Dice · · Score: 5, Interesting

    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.

  3. Re:Makes Sense, Actually by VGPowerlord · · Score: 4, Interesting

    When you really look at it, there's no reason that Adobe shouldn't embrace HTML 5.

    Yes there is. Right now, Adobe has locks on both the production and consumption sides of Flash. Notably, they periodically add features to Flash that anyone else who makes a flash editor or player doesn't support. Heck, the GNU Flash player, Gnash, is still back on Flash 7 with some features of 8 and 9; the current version of Flash is Flash 11.

    Adobe controls neither production or consumption sides of HTML5. They would just be a single developer making a product in this market segment.

    As a side point, Flash was originally created as a vector animation tool. Strangely, it became hugely popular, largely supplanting its parent, Macromedia (now Adobe) Shockwave.

    --
    GLaDOS for President 2016! "Well here we are again. It's always such a pleasure." -- GLaDOS, 2011
  4. Consistency by sehryan · · Score: 4, Interesting

    It surprises me that in all of the discussions about how HTML5 is going to murder Flash, the one thing that everyone overlooks is the exact reason why Flash continues to be popular - Cross-browser consistency.

    I mean, right now, you cannot expect any of the five browsers to display CSS2 consistently, and that spec has been around since 1998. Why is it that everyone expects HTML5 to be perfect out of the box on every platform?

    --
    The world moves for love. It kneels before it in awe.