Slashdot Mirror


A Skeptical Comparison of HTML5 Video Playback To Flash

gollum123 writes "Think we'd all be better off if HTML5 could somehow instantly replace Flash overnight? Not necessarily, according to a set of comparisons from Jan Ozer of the Streaming Learning Center website, which found that while HTML5 did come out ahead in many respects, it wasn't exactly a clear winner. They did find that HTML5 clearly performed better than Flash 10 or 10.1 in Safari on a Mac, although the differences were less clear cut in Google Chrome or Firefox. On the other hand, Flash more than held its own on Windows, and Flash Player 10.1 was actually 58% more efficient than HTML5 in Google Chrome on the Windows system tested. As you may have deduced, one of the big factors accounting for that discrepancy is that Flash is able to take advantage of GPU hardware acceleration in Windows, while Adobe is effectively cut out of the loop on Mac." gollum123 also links to additional tests indicating that Flash "does not perform consistently worse on Mac than on Windows."

55 of 391 comments (clear)

  1. GPU acceleration and Opera by sopssa · · Score: 4, Interesting

    The second test seems to forget that Flash added GPU acceleration in Windows, which dramatically drops CPU usage. It's not even small amount, it's 60%->12% with YouTube 720p video and most likely even more with 1080p. They've been working a lot with NVIDIA on it, which means more bad news for HTML5. I also installed those new NVIDIA drivers and newest Flash beta and full screen video is considerably smoother.

    And where's Opera in this test? They added HTML5 support in 10.5 final too and their whole drawing engine will be hardware accelerated, with websites also. Their canvas implementation is also faster than with any other browser.

    1. Re:GPU acceleration and Opera by shutdown+-p+now · · Score: 3, Informative

      Unless a biggie like Google /MS /Apple back on HTML5 i don't see why it would replace incumbent standard

      Both Google and Apple are heavy HTML5 backers. Not only they're on the W3C working group for it, but their respective browsers already implement large parts of it (including, specifically, HTML5 video).

    2. Re:GPU acceleration and Opera by Ethanol-fueled · · Score: 2, Interesting

      Will that get rid of those annoying but obligatory Quicktime downloads?

    3. Re:GPU acceleration and Opera by shutdown+-p+now · · Score: 2, Informative

      Well, Apple has been pushing for standardizing on H.264 as a primary codec for HTML5 video, specifically... so I guess that would make it "yes".

    4. Re:GPU acceleration and Opera by shutdown+-p+now · · Score: 4, Informative

      Well, I can't speak for Google, but Apple was one of three companies (two others being Mozilla and Opera) which founded WHATWG, thus putting a start to HTML5 development.

      Also, it doesn't make sense for them to "comply with the standard" when there's no standard yet. As it is, both Google and Apple (and others) are writing the standard, and implementing the current drafts. Google also provides HTML5 beta of YouTube. If, as you say, there is no real business case for them to promote HTML5, they wouldn't do either thing.

      The reason why Google touts Flash support in Android at the same time is because Flash is still relevant today, and because this is a major competitive advantage that Android has over iPhone. It would be foolish of them not to raise that point.

    5. Re:GPU acceleration and Opera by Aladrin · · Score: 5, Insightful

      So they're saying that when Flash isn't -doing- anything, it still sucks down 12% of the CPU. Yeah, that's awesome! Whoo!

      They're also saying that With Flash using the GPU to the hilt, and HTML 5 not, they use about the same CPU.

      Seriously, these are not impressive numbers.

      --
      "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
    6. Re:GPU acceleration and Opera by Runaway1956 · · Score: 3, Interesting

      From the submission: "On the other hand, Flash more than held its own on Windows,"

      "When was the last time Performance and better quality became critical in deciding which tech will be widely deployed?"

      Personally - I wish that SECURITY were the primary criteria in deciding which tech will be widely deployed. I'll sacrifice a bit of "performance", if HTML5 proves to be immune to all the exploits that Adobe products are open to. Yes, of course, HTML5 will have exploits, but Adobe seems to be wide open today.

      Yes, HTML5 supports "super cookies" - that's a potential exploit IMO. What else is there?

      Security, security, security. If a new technology opens an entire new class of exploits, then it's not worth having, even if it increases "efficiency" by orders of magnitude.

      That said - I favor HTML5, because it is "open", and people can manage their own risk. With Adobe being closed, the open source crowd isn't free to search for the exploits that the black had people keep finding.

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    7. Re:GPU acceleration and Opera by PopeRatzo · · Score: 4, Insightful

      I favor HTML5, because it is "open", and people can manage their own risk.

      Most people can't manage their own desktop, how they gonna manage their own risk?

      --
      You are welcome on my lawn.
    8. Re:GPU acceleration and Opera by IntlHarvester · · Score: 4, Informative

      I wasn't particularly impressed with the Youtube HTML5 beta (using Chrome) and ended up opting out. Playback wasn't very smooth, the video controls are slightly buggy, and HD videos seemed to take more time buffering. As of right now, the Flash player provides a far better experience.

      (And Youtube's player controls are probably far better than anything the average developer could come up with.)

      Internet nerds are predicting that HTML5 will be the death of Flash Video, but IMO it still looks like it has a long way to go.

      --
      Business. Numbers. Money. People. Computer World.
    9. Re:GPU acceleration and Opera by nahdude812 · · Score: 4, Insightful

      In the mean time, Mozilla has stated that they're unable to ship H.264 as part of Firefox. H.264 has patent and licensing issues associated with it.

      Your choices are still 1) create content once for a ubiquitous platform available absolutely everywhere except Apple embedded devices (where Apple chooses for you that you don't have access to it), or 2) create content multiple times in multiple formats, falling back on browser sniffing and other skulduggery, plus having to test on a variety of different platforms, then going ahead and creating the #1 version anyway since there are still people you can't reach without this no matter how hard you try.

      HTML5 is the right direction. But it is a long, long way from mature. There isn't a single ubiquitous codec even when your users support the fledgling standard otherwise. Until then, Flash is still the right choice for all but technical purists, both for video, and for absolutely everything else Flash offers (including feature domain HTML5 doesn't cover even in draft).

    10. Re:GPU acceleration and Opera by Skapare · · Score: 2, Insightful

      If NVIDIA would put the effort into making an open codec (such as Dirac) directly in the GPU firmware, and keep their Linux driver updated properly (or just open source it ... all the magic is in the GPU so the driver should just be a means to pass data between CPU and GPU), then an HTML5 based video would display well, too.

      This is NOT a showing of whether Flash is better than raw video, or not. It's a showing of what secret backroom deals can do to lock out safer, more secure, more open, ways of doing things, and doing them just as fast, if not faster. If speed really is the issue (and it's NOT number one for me), then show it honestly by putting an equal effort into both. They clearly failed to do that in this case.

      --
      now we need to go OSS in diesel cars
    11. Re:GPU acceleration and Opera by realityimpaired · · Score: 2, Informative

      .mov is a container format, like .avi. They can standardize on H.264 without giving up on QT. :)

    12. Re:GPU acceleration and Opera by Runaway1956 · · Score: 5, Informative

      Super cookies, yes. Maybe you have some? Read:

      http://www.imasuper.com/66/technology/flash-cookies-the-silent-privacy-killer/

      http://www.fightidentitytheft.com/blog/new-breed-super-cookie-defies-removal-almost

      http://lifehacker.com/5245418/betterprivacy-prevents-tracking-by-flash-other-super+cookies

      In short, if you don't know any better, Adobe enables web sites to install a cookie that your browser doesn't even know about, let alone manage. And, those cookies persist forever, tracking anything that the website chooses to track.

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    13. Re:GPU acceleration and Opera by devent · · Score: 2, Insightful

      In the mean time, Mozilla has stated that they're unable to ship H.264 as part of Firefox [mozillazine.org]. H.264 has patent and licensing issues associated with it.

      Isn't the codec the responsibility of a codec library? I played H.264 videos on Linux today. Mozilla could just use gstreamer or what ever else

      --
      http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
    14. Re:GPU acceleration and Opera by wisty · · Score: 2, Insightful

      It's just odd to compare two different tech stacks (which can do just about anything) by measuring their video playback performance.

      As long as hardware acceleration works, the language (or whatever you want to call it) is not a big factor. It's like comparing an apple (which may have a gorilla supporting it), in a cage match with an orange (which may have a gorilla supporting it).

      Flash uses the GPU (except on OSX - boo Apple). HTML5 will use the GPU on every platform sometime in the future. I know which one my money's on.

      I don't like it that HTML5 will win due to Apple's dirty tricks, but face it - sometimes the end justifies the means.

    15. Re:GPU acceleration and Opera by cheesybagel · · Score: 3, Interesting

      No need to bother. All that needs to happen is for someone to add CUDA or OpenCL acceleration to the codec playing and it will still be offloaded to the graphics card.

    16. Re:GPU acceleration and Opera by Runaway1956 · · Score: 3, Interesting

      Well - maybe it's not a direct equivalent, but yes, HTML5 has the potential to keep such persistent cookies, as large as or larger than flash now uses.

      http://completosec.wordpress.com/2010/02/07/html-5-persistent-offline-storage-as-a-risk-management-challenge/

      Or, you can just google "html5 persistent cookies" for more, and better hits. It's the "persistent" part that I'm concerned about, and the ability to find them, sort them, and manage them. Normal cookies aren't a problem for anyone with even minimal computer competence. These new Super Cookies are a problem for even moderately computer savvy people.

      --
      "Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br
    17. Re:GPU acceleration and Opera by Anonymous Coward · · Score: 3, Insightful

      n the mean time, Mozilla has stated that they're unable to ship H.264 as part of Firefox

      I wouldn't want them to. Why in the hell would any browser include a codec. What Mozilla and every other browser is supposed to do is not care about codecs and use what's installed on the user's computer. Place an option in the preferences menu, so you can choose between multiple installed options.

      I don't want to choose my browser based on who has the most efficient codec. I want to choose it based on which browser gives me a better browsing experience. If I find a better codec that can do GPU acceleration, or whatever, I want to install it and have all my browsers be able to use it.

    18. Re:GPU acceleration and Opera by jedidiah · · Score: 3, Insightful

      > It's just odd to compare two different tech stacks (which can do just about anything) by measuring their video playback performance.

      It's the point of comparison because hardware acceleration DOES NOT WORK.

      It doesn't work despite there meant a means to do so on both Linux and MacOS. Adobe continues to give same excuses while sandbagging.

      Their Windows version probably isn't even living up to it's own potential in this regard.

      Video playback performance is fixated on because it means the difference between being able to use an Atom or needing a 3Ghz or Quad Core machine.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    19. Re:GPU acceleration and Opera by nine-times · · Score: 3, Insightful

      In the mean time, Mozilla has stated that they're unable to ship H.264 as part of Firefox [mozillazine.org]. H.264 has patent and licensing issues associated with it.

      Why not just kick H264 over to a media player (VLC/Quicktime/WMP) instead of trying to include codecs in browsers? That's an option, at least, since most media players will decode h264.

      Here's the main problem I have with this complaint: Ultimately, Flash is just being used as a 3rd party H264 media player anyway. By saying people should stay on Flash, you're basically saying, "Mozilla can't distribute H264 decoders and we can't ask people to install any 3rd party H264 decoders, so instead we're going to force everyone to install a particular 3rd party H264 decoder which is included in a sprawling 3rd-party plugin that only works well in Windows."

      When you stop and think about it, it doesn't really make a ton of sense. Flash has worked as a stop-gap measure, but it really has never been a good way to handle things.

      create content once for a ubiquitous platform available absolutely everywhere except Apple embedded devices

      *sigh* If only it were that simple. Flash isn't on absolutely everything except Apple devices. It works pretty well in Windows. You can get it on Linux/BSD/etc, but some distros don't have it installed by default. Even on OSX, Flash is a buggy resource hog that crashes constantly, which is at least part of the reason why Jobs doesn't want it on his low-power devices. Non-Apple phones and embedded devices may or may not have Flash support.

      Adobe tried to blame Apple for the poor performance of Flash on OSX, but if you read their description of the situation, it basically comes down to, "We chose to stick with Carbon (an old framework which Apple has basically been trying to obsolete, but keeping around for compatibility's sake) instead of switching to Cocoa (the new framework), and Carbon doesn't have as direct access to the GPU."

      There isn't a single ubiquitous codec even when your users support the fledgling standard otherwise.

      H264 is getting to be pretty darned ubiquitous, close to how MP3 was for audio back in the heyday of Napster. Sure, you still had Real Media files and Windows Media files, but mostly people used MP3. Also, technically you're supposed to pay a patent licensing fee for distributing MP3 encoders, MP3 decoders, and even MP3 files, so it really isn't that different.

      So who doesn't use H264 to encode their movies? In my experience, it's mostly (a) people who use Ogg for ideological reasons rather than practical reasons; and (b) pirates who are under the mistaken impression that the old DivX encoder provides better compression than H264, or believe that H264 is a proprietary Apple format. Yes, I know there are other reasons to use other formats, but I think the two I mentioned probably take care of most of the normal consumer uses (ignoring legacy devices).

    20. Re:GPU acceleration and Opera by etymxris · · Score: 2, Insightful

      I don't see any fundamental difference between native support of jpeg and native support of video codecs.

    21. Re:GPU acceleration and Opera by Blakey+Rat · · Score: 2, Insightful

      If NVIDIA would put the effort into making an open codec (such as Dirac) directly in the GPU firmware, and keep their Linux driver updated properly (or just open source it ... all the magic is in the GPU so the driver should just be a means to pass data between CPU and GPU), then an HTML5 based video would display well, too.

      And... what would be in it for them? They're not going to spend all that money to get Slashdot bragging rights.

    22. Re:GPU acceleration and Opera by Bert64 · · Score: 3, Interesting

      Well if you look at web browsers on the Amiga platform, they typically had no built in support for any image formats whatsoever. The OS provided a facility called "datatypes" which allowed any application supporting datatypes, to load any format for which a valid datatype was available. Amiga browsers were among the first able to display PNG images on the web simply because a PNG datatype already existed.

      --
      http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  2. How much of a perfomance hit for open standards? by symbolset · · Score: 4, Interesting

    How much of a performance hit am I prepared to accept for open standards? 100%. The performance of the open platform will double every 18 months, but the DRM'd content will be forever limited.

    --
    Help stamp out iliturcy.
  3. This is early days for the video tag by javilon · · Score: 5, Insightful

    As soon as the video tag becomes popular implementations using the GPU will appear, and will not only work in Windows. We will be farther better off.

    And if Google open sources the VP8 codec the just purchased, it will be even better.

    --


    When his defense asked, "Which computer has Jon Johansen trespassed upon?" the answer was: "His own."
    1. Re:This is early days for the video tag by sopssa · · Score: 4, Insightful

      Actually, GPU acceleration is why Theora is losing to H.264 again. H.264 can be already hardware accelerated in almost every device from PC's to mobile phones. But Theora doesn't have such support.

    2. Re:This is early days for the video tag by FrostedWheat · · Score: 2, Interesting

      Theora doesn't need anywhere near as many CPU cycles to decode as H.264. Hardware acceleration would be nice, but it's not as critical as you'd think.

    3. Re:This is early days for the video tag by marcansoft · · Score: 3, Informative

      That's H.263, which is a horrible piece of crap. It's what youtube used before H.264 and they still do for the low-quality version of videos. There's no question that Theora beats the old flv H.263.

    4. Re:This is early days for the video tag by dingen · · Score: 5, Insightful

      Maybe not on a PC, but in a handheld device you really can't let the CPU do the decoding. You simply can't get the 10 hours (or so) of video playback on a phone that way with today's chips and batteries. A dedicated video decoding chip is the only option for such devices and right now, a chip for decoding MP4/H264 is already present in most systems.

      --
      Pretty good is actually pretty bad.
    5. Re:This is early days for the video tag by BeardedChimp · · Score: 4, Interesting

      Many system on chips such as the omap3530 have a dsp. These are general purpose and for example the omap3530 can do 720p h264 and mpeg4 decoding.
      However adding theora or vp8/6 decoding is a matter of writing a codec for the dsp as opposed to having to create a whole new decoder chip.
      Devices that use something similar could add this functionality through patching even after either vp6/8 or theora get some support.

    6. Re:This is early days for the video tag by EvanED · · Score: 2, Informative

      I have to respectfully disagree, even based on your clip. In particular, I notice a lot of artifacts around the edges of objects, especially when moving. Some times I wrote down as being particularly noticeable were 3:47, 4:13, and 4:31. The branch at 4:11 was a bit artifacty, and IMO the opening "The Peach Open Movie Project Presents" lettering wasn't even a contest between the two.

      I was watching both in VLC in full-screen mode on a 22" screen. I'm not convinced VLC actually has great quality, but I don't know of anything else I have that'll play Theora at the moment. I tried to do the test blind, even coming up with the script I pasted below (in case anyone else wants to try it; just change the 'theora' and 'h264' functions at top and run in Bash), but I bungled things a little bit and basically managed to spoil myself. I do think it's hard to compare a clip that's close to 5 minutes long; alternating between 10 second clips would be much better.

      In addition, the Theora version responds terribly to random seeks, with portions of the pre-seek image remaining on screen sometimes for several seconds. (I realize this isn't particularly relevant to the power needed for decompression, but it did mean that I couldn't just seek to the same place and compare, and it presents another practical objection.)

      function h264 {
      /cygdrive/p/Program\ Files\ \(x86\)/VideoLAN/VLC/vlc -f --no-video-title-show bbb_youtube_h264_499kbit.mp4
      }
       
      function theora {
      /cygdrive/p/Program\ Files\ \(x86\)/VideoLAN/VLC/vlc -f --no-video-title-show bbb_theora_486kbit.ogv
      }
       
      if [[ $RANDOM -le 16536 ]]; then
          printf "Press Enter to start...\n"
          read FOO
          while [[ $FOO != "no" ]]; do
              h264
              printf "Press Enter to start second video\n"
              read FOO
              theora
              printf "Again?\n"
              read FOO
          done
       
          printf "First: Theora\n"
      else
          printf "Press Enter to start...\n"
          read FOO
          while [[ $FOO != "no" ]]; do
              theora
              printf "Press Enter to start second video\n"
              read FOO
              h264
              printf "Again?\n"
              read FOO
          done
       
          printf "First: H.264\n"
      fi

  4. Flash DOES run slower on Mac by ottawanker · · Score: 2, Interesting

    From what I can tell by reading the article that says that 'Flash "does not perform consistently worse on Mac', what they really mean is that not only does Flash run slower on Mac, but Safari is also coded really poorly for Windows.

  5. Re:Flash aint so bad by gaelfx · · Score: 2, Insightful

    Well, for those of us interested in the development of Linux as a viable alternative to other operating systems, closed source software that comes to be considered "necessary" for general computer use means more time and resources spent on developing software against the de facto closed standards. Imagine if all those people trying to make Flash work on Linux could do something else with code that they can actually see. I dunno about you, but when I code for something, I like to know what the heck I'm working on and how it will fit in, rather than flying blindly at some goal.

  6. html5 is a clear winner by roman_mir · · Score: 2, Insightful

    HTML 5 is a clear winner by virtue of not being Adobe Flash or any other proprietary application but an open standard.

  7. Re:Why compare? by shutdown+-p+now · · Score: 3, Informative

    HTML5 hasn't even settled on a video codec

    They aren't goint to settle on it. It will be unspecified, just as image formats were in past HTML specs.

    how can there even be a real comparison here?

    You compare both platforms with the same codec, of course.

    Of course HTML5 can't take advantage of GPU acceleration yet, they don't even know what they'll be accelerating yet!

    If they don't know, how do they play it today?

    In fact, they do know. A de facto standard is already in place (Flash played a part in that as well), and it's called H.264.

    HTML5 hasn't had the chance to implement GPU acceleration and that maybe they should consider it as part of their criteria in their codec selection process.

    HTML5 doesn't implement acceleration, browser vendors do. It's not any harder for them to do so than it is for Adobe, so presumably, if Flash can hardware-accelerate, so can the browser. It's just that they didn't get to that point yet.

  8. Anecdotal evidence by Ma8thew · · Score: 3, Interesting

    Obviously this is anecdotal, but the fans on my Macbook pro often spin up playing full screen flash video, but never while playing video in Quicktime. But even if HTML5 performs no better than Flash currently, HTML5 still wins because it doesn't rely on Adobe to issue security and performance updates.

  9. Re:How much of a perfomance hit for open standards by EvanED · · Score: 2, Informative

    Since flash is not fully supported in 64-bit. 64-bit OS:es will not be able to be widely spread.

    There are a couple different problems with this statement... I'll just say that I'm posting this from a 64-bit OS and a browser that runs Flash just fine. (Well, as fine as a Flash can be run anyway, which is "not very", but that's sort of beside the point.)

  10. Tailspin by gd2shoe · · Score: 2, Interesting

    You've just described the tailspin that we're in. To get out of it, somebody must loose face because their device/system is incapable of supporting open and free standards. It's sad that the end users will be collateral damage to this, but the sooner it happens, the better off we'll be.

    --
    I won't join Slashcott. OTOH, If Beta goes live, I just won't be back until it's fixed. Sorry Dice.
  11. Check your sources... by diamondsw · · Score: 3, Informative

    gollum123 also links to additional tests indicating that Flash "does not perform consistently worse on Mac than on Windows."

    Yes, tests provided by... Mike Chambers of Adobe. I'm sure that they're completely impartial.

    When I turn on HTML5 video support at YouTube, the exact same clip in the exact same browser on the exact same OS on the exact same session runs at a third of the CPU power. Sure, it's an anecdote - and one that's been observed by hundreds if not thousands of others, consistently over the years. But according to Adobe, nope, no problems at all. Emperor's clothes look really chic.

    Fuck off, Adobe. You had years to improve your damn plugin, and we'll all be better off when it and its horrid performance and security record are no more.

    --
    I don't know what kind of crack I was on, but I suspect it was decaf.
  12. Let's wait and see by oljanx · · Score: 4, Insightful

    It's not really fair to compare a technology that is still being developed to others that are very well established. The big benefit of HTML5 is it's non-proprietary nature. Once the standard is adopted and applications are built around it these comparisons will look very different.

    1. Re:Let's wait and see by IamTheRealMike · · Score: 2, Insightful

      I don't think openness of the standard is a benefit in this specific instance. Flash has to be optimized once per platform (so, 3 times). HTML5 video has to be optimized once per browser per platform, which is considerably more work. If only one popular browser doesn't do a good job, HTML5 video will be an unsuitable solution (because that browser will still need to use flash, and at that point you might as well deploy flash for everyone).

    2. Re:Let's wait and see by Taevin · · Score: 2, Informative

      Except that Adobe have said they do want to fix it, but can't, because Apple refuses the provide the APIs they need.

      Which is clearly bullshit. Adobe is claiming that Apple won't give anyone access to hardware acceleration APIs, and yet I have a number of games and video players that seem to work just fine. The problem is that Adobe refuses to use the available APIs for video acceleration. Why do you think Flash runs at 100% CPU on every platform (I guess not on Windows now that they have figured out some kind of acceleration)? Adobe insists on using their own, poorly written, software decoder.

      Adobe could just send their h264 stream through the QuickTime API, or probably write something else using one of the Core APIs (Core Video, in particular, provides GPU rendering). Instead, apparently, they'd rather sit around bitching about how Apple won't write an API around their application.

    3. Re:Let's wait and see by IICV · · Score: 2, Interesting

      I don't think openness of the standard is a benefit in this specific instance. Flash has to be optimized once per platform (so, 3 times).

      But Flash has been optimized zero times per platform. It is under the sole control of Adobe, so unless you have some mystical way of improving their legendarily shitty code, Flash is simply not going to get any better ever. Adobe has exactly zero reason to make Flash work any better, because they have zero competition in the market (Silverlight? Don't make me laugh, at this point everyone knows what happens when you take up a Microsoft standard). Because Adobe has no competition, Flash just keeps on getting worse and worse and taking up more and more CPU, which is totally unsupportable in theoretical future low-power web devices. Apple refused to include Flash support in the iPhone and the iPad for a very good reason; it absolutely kills performance, even on a full-blown computer.

      On the other hand, if we put control over the implementation of this sort of thing into the hands of the browser companies, we'll see drastic improvements. Apple really wants a speedy, energy efficient yet full-featured browser for its mobile devices; Google wants a browser that can do more than modern ones for its web apps; the Mozilla foundation wants something like HTML 5 because it would fit in with their ideology far better than the current closed browser plugin; Opera wants it because their main market nowadays is mobile web, so their requirements are basically the same as Apple's. All of these companies have very good reasons for implementing something like HTML 5, and they all want you to use their browser - so we're going to see a lot of competition in terms of efficient HTML 5 implementations, just like we've been seeing a lot of competition in terms of efficient Javascript implementations.

  13. Retro machines by stimpleton · · Score: 2, Insightful

    By saying "PC and MAC", TFA disregards handheld and small devices. These may be dominant players in the medium term(till they are as powerful as PC's and Macs). HTML5 may have an edge, especially with the iPad attitude of limited Flash support

    --

    In post Patriot Act America, the library books scan you.
  14. Misses the point by gweihir · · Score: 3, Insightful

    Performance is rather secondary. This is about standards and cross-platform compatibility. Flash is an atrocity in this regard, and the earlier it gets tossed out on the trash heap of computing history, the better.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  15. Re:standardize a codec for html5 or die trying by EvanED · · Score: 2, Insightful

    This is an issue for browsers like Firefox.

    "Only" because Firefox refuses to use something like DirectShow to use whatever codecs are available on the system.

    See here for why; they aren't necessarily bad reasons, but changing their opinion on this matter would largely solve the H.264 codec patent issue as far as Firefox is concerned.

  16. Re:I've yet to see HTML5 video work by AresTheImpaler · · Score: 3, Informative
  17. Not a crap article by Macka · · Score: 3, Informative

    The author implies that adobe can't use gpu for flash on mac. Why not?

    It's not a crap article because it's true. If you look at the 10.1 public beta release notes it says:

    In Flash Player 10.1, H.264 hardware acceleration is not supported under Linux and Mac OS. Linux currently lacks a developed standard API that supports H.264 hardware video decoding, and Mac OS X does not expose access to the required APIs. We will continue to evaluate adding the feature to Linux and Mac OS in future releases.

    How Apple react to this will be a good litmus test of how fair Steve J is prepared to be with Adobe. Will he make the APIs available to benefit his customers but risk making HTML5 less attractive, or will he just ignore them and play hard ball.

    As for Linux, the historical lack of a unified approach to solving this (that includes all interested parties) is going to leave us out in the cold for some time yet. Let's hope that Gallium3D sticks, gains enough traction and doesn't get dropped for something else a few years down the road. That will make a nice change!

    1. Re:Not a crap article by JonJ · · Score: 2, Insightful

      Why can't they do this via the Quicktime APIs that expose hardware acceleration to H.264?

      --
      -- Linux user #369862
    2. Re:Not a crap article by TheRaven64 · · Score: 5, Informative

      It's not quite true on OS X. There is a standard way of playing back H.264 using hardware acceleration: use QuickTime. Adobe can't use this because they ship their own H.264 implementation (which is slower than the QuickTime one and ffmpeg), rather than using the supplied one. There aren't hooks for adding GPU acceleration to arbitrary CODECs, unless you use OpenCL, but there are APIs for playing back H.264.

      --
      I am TheRaven on Soylent News
    3. Re:Not a crap article by heffrey · · Score: 2

      You need to take off your blinkers. Windows is a great platform for developers and has been stable for around 20 years. Can't say the same for either Mac or Linux.

  18. Re:Halp! I are teh stupidness! by flyingfsck · · Score: 3, Informative

    MPEG2 compresses by a factor of about 5 to 10, while H.264 AVC compresses by a factor of about 20 to 30 and the subjective quality is better too, being not blocky.

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  19. Honestly by trifish · · Score: 5, Insightful

    I don't care if Flash is 50% faster than HTML5 video. I don't want the vulnerability-laden Flash on my primary OS just to watch a YouTube video. Period.

  20. Re:I've yet to see HTML5 video work by hairyfeet · · Score: 3, Interesting

    I don't know about him but I tried your link on my netbox, a 1.8GHz Sempron running XP Home, and it kept the CPU redlined while the video was a slideshow, even though the video was just a tiny slice on the screen, while only having two tabs open (this page and the video). Meanwhile Youtube H.264 in SD plays just fine full screen and plays nicely even with multiple tabs open.

    Was that the point you were trying to make? Or was it that the link you provided was to a "better" HTML5 player? Because if I'm gonna have to fire up my quad just to watch a video in HTML5 I'll stick with Flash, thanks anyway. I can always slap a cheap 4650 into the AGP slot if I want to get HD on this single core PC, thanks to hardware acceleration. Can I do that with HTML5?

    --
    ACs don't waste your time replying, your posts are never seen by me.
  21. Re:I've yet to see HTML5 video work by lawyer+boy · · Score: 2, Interesting

    Playing the video on my MacBook Pro resulting in Safari going from 5% of CPU to 20%. Clearly, YMMV.