Slashdot Mirror


Ars Thinks Google Takes a Step Backwards For Openness

An anonymous reader writes "Over at Ars Technica, Peter (not so) Bright gives a long-winded four pages of FUD about how Chrome dropping support for H.264 is a slight against openness. 'The promise of HTML5's video tag was a simple one: to allow web pages to contain embedded video without the need for plugins. With the decision to remove support for the widespread H.264 codec from future versions of Chrome, Google has undermined this widely-anticipated feature. The company is claiming that it wants to support "open codecs" instead, and so from now on will support only two formats: its own WebM codec, and Theora. ... The reason Google has given for this change is that WebM (which pairs VP8 video with Vorbis audio) and Theora are "open codecs" and H.264 apparently isn't. ... H.264 is unambiguously open.'"

10 of 663 comments (clear)

  1. Re:So, h264 is by unity100 · · Score: 1, Informative

    so, its not free, and open.

  2. Re:So, h264 is by SuricouRaven · · Score: 4, Informative

    The standard is open, and there are open source encoders and decoders. So in that sense, it's open: Everything is fully and publicly documented. However, it is also covered by hundreds of patents, which means you can't actually use any of that information without getting a licence from the patent holders. One of whome is Microsoft, who stands to make a lot of money from it. Others include Sony and Apple, who stand to make a lot too. So far the consortium that administers the patent pool has been quite reasonable about terms - free for noncommercial use, low costs even for commercial - but there is a fear that if x264 were to become so established it were impossible to do without it then there would be a temptation for them to start milking more money from those patents.

  3. Re:So, h264 is by jgagnon · · Score: 5, Informative

    WebM and Chrome are both open sourced under public licenses. To say Google "owns" them is to not understand how these open licenses work. Also, the patents behind VP8 have been released, irrevocably, to the public.

    --
    Remember to maintain your supply of /facepalm oil to prevent chafing.
  4. Re:excuse me by drinkypoo · · Score: 5, Informative

    cut bullshit. a standard that is not open, and subject to licensing fees, is NOT open. you cant redefine open.

    Well then perhaps you should stop trying to do so. Open means documented and interoperable, it does not mean patent-unencumbered. It means you can see what is happening and make changes, but it doesn't guarantee you the right to redistribute those changes, which is why we need a distinction between Open and Free software and why the OSI is the enemy of Free Software; it attempts to conflate the two by redefinition of the term "Open" to mean something almost-but-not-actually like Free Software and dilutes it.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  5. Re:Summary sucks. by rubycodez · · Score: 3, Informative

    Your linked article states that it does lead to mass death of brain cells in heavy drinkers.

    It would be more accurate to state that occasional moderate use of alcohol is not known to kill brain cells, but heavy chronic use can.

  6. Re:Summary sucks. by kangsterizer · · Score: 3, Informative

    Slashdot is moderated by the users. you can downrank entire stories.
    If many people uprank this story, it means most are ok with the contents.

    Of course you need nice karma to be able to moderate that stuff. But hey. Slashdot is still the best large volume user moderated news site i know by light years. I can't count how many website comment and story moderation process is utterly useless and crappy in comparison. (even if bashing slashdot is normally a karma setter .. on slashdot :P)

  7. WebM has critical mass by qmaqdk · · Score: 2, Informative

    The browser market share in Europe is FF 38.11%, Chrome 14.58%, Opera 4.57%, all of which either support or will support WebM. That's 57% of the browser market, and if YouTube goes WebM IE and Safari will have no choice but to support it as well.

    Also since FF cannot include H.264 that means encoding your video in H.264 instead of WebM costs you nearly 40% of users.

    --
    My UID is prime. Hah!
  8. Re:Putting the snideness of the summary aside... by kangsterizer · · Score: 3, Informative

    FOSS doesnt force you to use their software, and doesn't force you to use only their software if you do use some of it.
    On the contrary, proprietary software forces you into many things (including the fact that you don't even own the said software you pay for).
    So you're free, you can use FOSS or not, with or without proprietary software that permits it. There is no *you have to use FOSS* *put gun on your head*.

    On the other hand... FOSS usually still recommands using only FOSS because there's no restrictions (unlike proprietary software).

    Is that so hard ?

  9. Interesting article about video format for HTML5 by dalmor · · Score: 3, Informative

    Most people don't know that in order to support EVERY video format for HTML5, you still have to encode a video 3 different times. But this site has a great explanation on which browsers support what, this history of the video formats, and even describes the history of licensing HTML5(i.e. went from paying for encoders, players, AND transmitting to just paying for encoders to players).

    http://www.diveintohtml5.org/video.html

  10. Re:I do think people need to understand that by cr_nucleus · · Score: 4, Informative

    You're completely missing the point.

    Nobody cares about a single codec. Someone makes a good proprietary codec ? Good for them !

    The problem arises when it becomes a required base part of the web.

    Remember the GIF debacle ? Remember that many open source image editor did not have the capability to save gif images ? That's exactly what is at stake here.
    Have one company control a base standard of the web makes it control who can or cannot create the tools to create web content. Of course big players like Google or Mozilla have the funds to pay royalties, but what about that guy who made a simple command line tool to split/merge h264 videos ?

    You can argue that the MPEG-LA has made the codec royalty free but truth is they can instantly make it illegal to open source any software using h264.

    That's what the fuss is all about, not just throwing two bucks at a video codec.