Image Source: gizmoray.com An interesting item today that doesn’t exactly support the whole ‘Google staunch defender of open-ness’ theory. As John Gruber at Daring Fireball has talked a lot about, Google are dropping support for the H.264 video compression standard in their Chrome browser. Here’s a comment on that from Slashdot: Znu”, on Slashdot: This […]
" />

So How Does that Google Open, Apple Closed Argument Go Again?

GoogleVApple

Image Source: gizmoray.com

An interesting item today that doesn’t exactly support the whole ‘Google staunch defender of open-ness’ theory.

As John Gruber at Daring Fireball has talked a lot about, Google are dropping support for the H.264 video compression standard in their Chrome browser. Here’s a comment on that from Slashdot:

Znu”, on Slashdot:

This serves two strategic purposes for Google. First, it advances a codec that’s de facto controlled by Google at the expense of a codec that is a legitimate open standard controlled by a multi-vendor governance process managed by reputable international standards bodies. (“Open source” != “open standard”.) And second, it will slow the transition to HTML5 and away from Flash by creating more confusion about which codec to use for HTML5 video, which benefits Google by hurting Apple (since Apple doesn’t want to support Flash), but also sucks for users.

I’m far from knowledgeable on all the various web standards in play in Google’s decision on H.264, but it sure doesn’t sound like the big ‘open’ play from what I can gather by reading today.

Continue reading:

TAGS: