News for hackers. Stuff that matters.
Re:Chromium Blog: More about the Chrome HTML Video Codec Change by ZeroGravitas on Saturday January 15, 2011 @04:47AM (#2106770)
So this is a bad decision because one technology you like is already entrenched so there's no point fighting it, and also a bad decision because another technology you don't like is so entrenched that it'll be around for years because Google won't fight it (in one very particular way, which happens to benefit Apple most).

Many of your arguments are valid against WebM (basically lack of maturity, support) but the exact same arguments can be made about HTML5 video with any codec (not supported by the majority of bowsers, it's not a standard yet, where is the DRM, hardware acceleration is patchy, captioning support is still sketchy, easy switching between streams etc.)

The set of those who oppose Flash as a closed web technology yet don't believe in royalty-free web standards is much larger than I thought it would be. But it seems to be mostly the cultier end of the Mac fanbase. It's a bit of a shame that they can't just come out and say "this affects me because Apple supports neither the current defacto standard H.264 via Flash, nor the coming de jure standard WebM via HTML5 on my portable iOS devices". (Note that the more normal Apple users were already annoyed, at Apple, for the first half of that lack of support on their iPads.)

Flash is in no-way teetering on the brink, and this decision by Google has minimal impact compared with the fact that 99% of web video is served via Flash. The only thing likely to make a dent in that number is changes at Youtube. So if you really hate Flash that much, I'd stay on their good side.

Re:Chromium Blog: More about the Chrome HTML Video Codec Change by bonaldi on Saturday January 15, 2011 @07:29AM (#2106897)
That's such an uncharitable reading I don't really know where to start. It's a bad decision because its only real-world consequence is to entrench Flash even further.

It does that by ignoring the state of play of video content, which is what could have driven the change to HTML5. To those guys it's as though they removed support for JPEG, frankly.

What's more, there are real, sensible, pragmatic arguments against doing this, and they don't all boil down to "wah but I has iPad". If anything, the iOS users are going to be absolutely fine out of this, because they're already where people with video content need them to be.

The only losers are people who would like HTML5's video tag to replace Flash as widely as possible. That's why Adobe is delighted.