Slashdot Mirror


HTML 5 Takes Aim At Flash and Silverlight

snydeq writes "While Adobe, Microsoft, and Sun duke it out with proprietary technologies for implementing multimedia on the Web, HTML 5 has the potential to eat these vendors' lunches, offering Web experiences based on an industry standard. In fact, one expressed goal of the standard is to move the Web away from proprietary technologies such as Flash, Silverlight, and JavaFX. 'It would be a terrible step backward if humanity's major development platform [the Web] was controlled by a single vendor the way that previous platforms such as Windows have been,' says HTML 5 co-editor Ian Hickson, a Google employee. But whether HTML 5 and its Canvas technology will displace proprietary plug-ins 'really depends on what developers do,' says Firefox technical lead Vlad Vukicevic. It also depends on Microsoft, the only company involved in the HTML 5 effort that is both a browser developer and an RIA tool developer. 'That's a big elephant in the room for them because you can imagine the Silverlight team [whose] whole existence is to add [this] functionality in. [But] if Internet Explorer puts it already in there, why do we have Silverlight?' asks Mozilla's Dion Almaer." The RIA guys are quoted as saying they're not worried, because HTML 5 + CSS 3 is 10 years out. Are they just whistling in the dark?

11 of 500 comments (clear)

  1. Re:It's the tools stupid by CountOfJesusChristo · · Score: 5, Interesting

    If graphics artist types can't make the kind of pointless crap that they do now with Flash, we won't see uptake of HTML 5.

    I was under the impression that canvas tag was going to allow people to create those kinds of whiz-bang interfaces that are currently done in flash.

  2. HTML5, with canvas, is fantastic by Radhruin · · Score: 5, Interesting

    I've recently embarked upon a hobby project where I'm only targeting the latest browsers, excluding IE8.

    Not until now have I realized how much we web developers are hampered by IE. Canvas and Javascript are a highly capable platform for interactive graphics, and it works across browsers and operating systems without issue. Chromium on Linux for example, incomplete as it is, works with canvas out of the box (not to mention about 10 times faster than FF in executing Javascript).

    The ability to create web pages quickly, using convenient CSS2 and 3 rules, the ability to use piles and piles of Javascript without worry, the ability to have everything just work across my target browsers, it's utterly amazing. If we weren't stuck in this damn backwater due to having to support IE, the web would be a far more compelling platform.

    I absolutely cannot wait for the day when HTML5 and CSS3 are widely supported and adopted, but will that day ever come? Surely Microsoft realizes, as I have, how much potential is here, and I don't doubt that some of the higher ups would hold IE back so that developers are forced to use their plugins in order to deliver their content.

    For those projects that don't care about IE support, HTML5 canvas/video/audio is a fantastic leap forward for the web. For the rest, business as usual for some time to come I'm afraid.

  3. Re:It's the tools stupid by nausea_malvarma · · Score: 4, Interesting

    In this day and age, you don't need to know good html in order to make a webpage. We have WYSIWYG editors. So I don't see why we couldn't have an editor for the canvas tag, that would provide artists with a point and click interface like flash does.

  4. RIAs have common runtimes, browsers do not by javacowboy · · Score: 5, Interesting

    The big problem with HTML5/JavaScript/CSS is that each browser has quirky behaviours that need to be tested. Even if Internet Explorer no longer existed, developers would have to test against Firefox, Safari, Chrome and maybe Opera. An example of a quirk is Safari not recognizing table element widths in percentages. A Flash developer tests against one Flash runtime, same with a Silverlight developer and a JavaFX developer.

    Adobe released a beta of a multiple browser runtime testing tool, but it's apparently very flawed.

    So until the above problems are solved, many RIA developers will simply use Flex, Silverlight or JavaFX, instead of coding for a hodge-podge of different browsers.

    --
    This space left intentionally blank.
  5. Re:It's the tools stupid by JobyOne · · Score: 4, Interesting

    If graphics artist types can't make the kind of pointless crap that they do now with Flash, we won't see uptake of HTML 5.

    As a professional "graphics artist type" I take a offense at that. What if I were to ask about the computer coders types making the kind of buggy crap they do now with [whatever language you like]?

    Don't blame me for the ugly crap made by my less talented brethren and I won't blame you for the unstable, insecure crap made by yours. No-talent assclowns are no-talent assclowns, regardless of profession.

    This graphics artist type (full disclosure: I may get paid for design, but my hobby is programming so I'm sort of an odd duck), for one, is very excited at the potential of HTML5. I look forward to a world where I can make animations for the web and embed videos and whatnot without having to muck around with stupid Flash/Silverlight/Java/whatever. I HATE Flash, I HATE Silverlight more, I HATE Java the most, and anything I can't name off the top of my head can go STRAIGHT to hell. I do see where the parent is coming from though. I see a lot of designers building sites in Flash just because they lack the analytical skills to wrap their overdeveloped right hemispheres around using CSS and (X)HTML. To design a website that isn't just pretty, but is actually good takes more than a good creative sense.

    These days everyone and their brother and their cat might think they're a web designer, but most of them aren't. They're just some guy with a pirated copy of Photoshop. Rest assured that there are web designers out there who know what they're doing.

    --
    Porquoi?
  6. Isn't search a factor? by caywen · · Score: 4, Interesting

    One factor I'd think would contribute greatly to the success of one over the others is how well a search provider like Google can reasonably analyze and index the content.

  7. WebKit vs. IE by Anonymous Coward · · Score: 5, Interesting

    For the past two years, I've been telling everyone the new browser war is between IE and WebKit. WebKit has become the default platform for the mobile browser market (iPhone using Safari and Android and Palm using their version). One of the big reasons Apple started WebKit was to keep the browsing platform out of the hands of a single vendor. It's not that Apple doesn't like proprietary technology. It's that they don't like proprietary technology that they depend upon and don't control.

    The battle for HTML 5 vs. Silverlight vs. Flash will be on the mobile platform. It's easy for Silverlight and Adobe to create a desktop application that work with 90% of the desktops (and a bit more work to get another 9%). However, the world is changing. Adobe and Microsoft can't create Silverlight and Flash clients for every single possible mobile platform. The trick is to get enough HTML 5 clients out there that it'll be worth it for developers to learn HTML 5. If enough developers pick up HTML 5, companies will make IDEs for HTML 5.

    If that happens, Flash and Silverlight will go away. The other possibility is that Apple will buy Adobe and open source Flash. Apple loves open source standards because it means that they'll be able to sell all the neat gadgets that work with these standards.

  8. Re:It's the tools stupid by RobNich · · Score: 4, Interesting

    I don't see why it would be less profitable. They don't charge for the Flash client, only for the authoring tools.

    Even if Silverlight were to take over, as long as Adobe makes a decent tool for creating Silverlight projects, they'll make close to the same amount. Although come to think of it, they may lose some sales only because they don't "own" the technology in consumers' eyes, and many consumers would buy Microsoft if they could anyway.

    But since HTML5 is not owned by a company, it puts Adobe on equal footing with any other company making an editor. Consumers would be able to choose their editor, and Adobe has a well-established footing in the market. If they just changed their product to output HTML5 instead of or in addition to a swf file, they'll keep their strangehold on the editor market.

    --
    Hello little man. I will destroy you!
  9. Sun uses Flash by jasonmanley · · Score: 4, Interesting

    I wonder what it says about JavaFX that Jonathan Schwartz's blog uses Flash for its video?

    --
    http://projectleader.wordpress.com
  10. Flash is de-facto standard for a reason by Ilgaz · · Score: 4, Interesting

    That huge framework install with all the functionality still hurts quicktime, in case of Windows Media, you have already got it forcibly installed and it also uses undocumented goods of Windows to perform better. Linux? No official support. Real? Well, people still think it is spyware even while it is open source.

    All these tools are in fact superior to Flash for embedding video, especially Real Player is really in 11th generation. Why they fail? Because they don't have Adobe design tools for use of real artists (designers) and they are still STUPID (hear me Apple) to add additional stuff to that already bulky download.

    I always feel sad for using Flash to embed videos with the functionality missing from it but as I can't tell people to "download 30 mb application" or "give up your IE and use that open source browser" (sorry!), I embed Flash.

    That was my point. Quicktime is a great technology being wasted by couple of idiots at Apple Inc. You know, the idiots insisted on asking $$$ for full screen playback for years. They couldn't seperate the "player" and "recorder"... They owned 80% of video market share back in worst days of Apple, can you believe?

  11. Re:400M Silverlight installs by Dragonshed · · Score: 5, Interesting

    Major League Baseball Advanced Media totally botched the transition not once, but twice. When switching from Flash to Silverlight last year their new Silverlight-based streaming player didn't work, leaving paying customers without service for days. This year they decided to switched back to a Flash-based player ON OPENING DAY. Unfortunately, the new player doesn't work either, and in many ways was worse than the silverlight player, requiring additional installation plugins for HD capabilities, and left these same paying customers without the opening day experience they're paying for two years in a row.

    New York Times Reader was a different case. It worked fairly well, but NYT got thoroughly flamed for introducing the reader for windows only, basing it on WPF's FlowDocument capabilities which aren't available for the Mac. Similar text features are eventually going to make it into Silverlight, but things like Printing are a much higher priority for the SL guys. The silverlight version of the reader used a complicated templating system rather than true adaptive text layout. Adobe's Text Layout Framework may not have been the first to market, but that + Flex + AIR are the first to bring it to a wider audience and may ultimately resonate more.

    Also I'm sure politics played a prevalent role in both cases, especially in the case of NYT where the Mac User's vitriol for anything microsoft played out.

    MLB 2008
    http://www.pcworld.com/article/144035/mlbs_web_video_strikes_out_on_opening_day.html

    MLB 2009
    http://www.huffingtonpost.com/robert-j-elisberg/major-league-baseball-str_b_185158.html

    NYT:
    http://www.itwriting.com/blog/1424-new-york-times-switches-from-wpfsilverlight-to-flash-for-reader-2.html