Live data from Hacker News

Google Removing H.264 Support in Chrome

blog.chromium.org

41–50 of 358 posts

Re: Google Removing H.264 Support in Chrome

#41
post #18
post #8

What the hell? It's sad that Google's corporate strategy is starting to override what's in the best interests of it's users. Web video is finally, after so many years, actually encoded in H.264. Who besides YouTube uses WebM or Ogg? I'll be going back to Safari if this happens.

An open solution isn't the best interest of the users? Surely this is just like Apple not supporting Flash in the hope that people go create HTML5 stuff which is open. Both companies have taken strategic and gutsy moves that will temporarily inconvenience users in the hope that long-term it pays of to both the companies and the users.

> An open solution isn't the best interest of the users?

An ubiquitous solution is in the best interests of users. My parents could care less about whether the video is encoded in H.264 or Ogg. They just want it to work on their iPad.

> Surely this is just like Apple not supporting Flash in the hope that people go create HTML5 stuff which is open.

It's not the same at all. Google, through YouTube and Chrome, helped make H.264 the defacto standard it is. Now they are trying to pull the rug out from under it. Apple never had support for Flash. Not to mention that Flash is a POS and doesn't work well on mobile devices anyways.

> Both companies have taken strategic and gutsy moves that will temporarily inconvenience users in the hope that long-term it pays of to both the companies and the users.

Long-term this isn't a game that Google wins. They've inconvenienced their users and the web will go on with H.264.

Re: Google Removing H.264 Support in Chrome

#42
post #17

The choice has been made by many places to simply use h264 video via the HTML5 tag to hit the iPhone/iPad and then fallback to a Flash video player which can easily play the h264 source video. Content producers would rather encode videos once, which is why they moved to FLV in the first place. There's no incentive to use anything else here. This hurts users. I am all for standards, but not for hurting users. And like…

Why doesn't Apple just include WebM support? It's an open codec...

Since when has Apple supported open standards simply because it makes sense to do so? Apple almost invariably chooses closed over open.

Re: Google Removing H.264 Support in Chrome

#44
post #16

Fantastic. Much as I enjoyed Burn All GIFs back in the day, I don't think Burn All H.264s sounds nearly as catchy or fun. Glad Google is doing the Right Thing on this front -- however convenient or entrenched they might be, hairy patented messes like H.264 have no place on an open web.

I'm just having a hard time understanding why they're ok with bundling the Flash player with Chrome, but not carrying an h264 decoder.

Re: Google Removing H.264 Support in Chrome

#45
post #17

The choice has been made by many places to simply use h264 video via the HTML5 tag to hit the iPhone/iPad and then fallback to a Flash video player which can easily play the h264 source video. Content producers would rather encode videos once, which is why they moved to FLV in the first place. There's no incentive to use anything else here. This hurts users. I am all for standards, but not for hurting users. And like…

Why doesn't Apple just include WebM support? It's an open codec...

My guess is patents. And they already have great H264 implementations. And hardware support.

What would be the benefit, to them or their users, if they used WebM?

Re: Google Removing H.264 Support in Chrome

#46
post #17

The choice has been made by many places to simply use h264 video via the HTML5 tag to hit the iPhone/iPad and then fallback to a Flash video player which can easily play the h264 source video. Content producers would rather encode videos once, which is why they moved to FLV in the first place. There's no incentive to use anything else here. This hurts users. I am all for standards, but not for hurting users. And like…

Why doesn't Apple just include WebM support? It's an open codec...

That would imply decoding in software. H.264 is currently decoded in hardware on those devices.

Re: Google Removing H.264 Support in Chrome

#47
post #17

The choice has been made by many places to simply use h264 video via the HTML5 tag to hit the iPhone/iPad and then fallback to a Flash video player which can easily play the h264 source video. Content producers would rather encode videos once, which is why they moved to FLV in the first place. There's no incentive to use anything else here. This hurts users. I am all for standards, but not for hurting users. And like…

You can equally argue that Apple's stance on video and on Flash is hurting users.

Re: Google Removing H.264 Support in Chrome

#49
post #17

The choice has been made by many places to simply use h264 video via the HTML5 tag to hit the iPhone/iPad and then fallback to a Flash video player which can easily play the h264 source video. Content producers would rather encode videos once, which is why they moved to FLV in the first place. There's no incentive to use anything else here. This hurts users. I am all for standards, but not for hurting users. And like…

Why doesn't Apple just include WebM support? It's an open codec...

Keep in mind Apple devices have HARDWARE h.264 decoders. It may not be as simple as you think.

Re: Google Removing H.264 Support in Chrome

#50

Earlier quoted context omitted.

Why doesn't Apple just include WebM support? It's an open codec...

Since when has Apple supported open standards simply because it makes sense to do so? Apple almost invariably chooses closed over open.

Apple is fully behind HTML5 - http://www.apple.com/html5/
Post reply on HN