Image Image Image Image Image Image Image Image Image Image

Winextra | May 19, 2013

Scroll to top

Top

Is Chrome turning into Google’s IE6?

Is Chrome turning into Google’s IE6?

Anyone who has been involved in the technology field, especially web technologies, will remember the horror of Internet Explorer 5; and Microsoft considering itself the arbiter of what web standards should be. It is only today that we are really seeing any serious decline in the use of IE6 but some would say that the price we have paid during those intervening years was too high.

Much credit has to go to both Firefox and Chrome, as well as the upcoming release of IE9, in finally being able to put a stake through the heart of the beast that was IE6. However those rescuers from a fractured web are themselves having problems.

Firefox has in the opinion of many web developer’s eyes, and regular users, become bloated and seeming to be travelling down it’s own path of standards (just ask Paul O’Flaherty, my partner on the Daily Brief show). In many cases it is Firefox that is losing marketshare to Google’s Chrome browser, rather than Internet Explorer losing ground.

But now we have Google stating that it is going to drop support in their browser for one of the core web video technologies, the H.264 video codec, in favor of trying to promote a more “Open Web” video codec that being it’s own  WebM video codec.

It is a codec that Google themselves owns but have made open but stills develop internally; and as many people have pointed out, isn’t as widely adopted as Google would like everyone to believe.

I’m not going to pretend that I know the ins and outs of all the different codec and who supports what as there are smarter people than me already doing that. What I do worry about though is Google has decided that because of it’s marketshare on the web that they can dictate, or heavily influence, what the web standards are going to look like going forward.

We’ve been down that road before and it has taken the better part of ten years for the Web to recover from one company’s heavy-handedness, do we really need to go through that all again?

Do we really need another IE6?

  • http://tech.gtaero.net/ Navarr Barnier

    Um, what.

    Wasn’t the IE6 chronicle the incredibly weird thing of ActiveX coupled with “who the hell can compete with that?”

    I don’t think Chrome dropping h264, which though the licensing restrictions have been loosened is still an owned codec and isn’t entirely free on and off the web, in favor of (NOT ONLY) WebM but ALSO OGG Theora, is a bad thing with them trying to say “haha, we’re the majority we declare whats best.”

    If they were dropping Theora as well, then you know we’d have some issues.

    Everything Google has done in the web browser space has been pushed to Open Source projects (so far as I know. Though I’m not 100% here, isn’t V8 Open Source?) and yet its Microsoft’s Internet Explorer and Apple’s Safari browser that don’t have Native support for any codecs other than h264.

    Is it really Google that we need to be afraid of?

    I think not.

    In conclusion, I don’t really see a point to this article.

    • http://www.winextra.com StevenHodson

      A good honest reply Navarr – thanks. See my reply to Paul for more thoughts on this.

  • http://pauloflaherty.com Paul OFlaherty

    Have to disagree with you here Steven. Chrome can never be another IE6 as it is simply lacking the market share to have that kind of influence. If Google drops support for the standards that everybody uses they will loose both user and developer support. There are simply too many other viable options for users for Google to play “big dick on campus” with regards to web standards.

    • http://www.winextra.com StevenHodson

      I think I am more referring to the mindset here rather than a direct correlation to IE6. Google has decided that it is in it’s best interest to drop support for a core web video codec, that as I understand it also has implications for HTML5. In return it is pushing its own web video codec as well as OGG Theora and I have yet to see any valid reasoning for this move.

      They are in effect trying to influence the direction that web video will take and it primarily relies on their own codec.

      That bothers me.

      • http://pauloflaherty.com Paul OFlaherty

        Google is very clear that they only want to support “open” codecs and standards, which on the face of it is great. However the codecs in question are inferior, and will have a hell of a time on mobile devices which currently have dedicated h264 decoders.

        Begs the question of when Google are going to nix their deal with Flash and remove support from Chrome if they are pushing “open”.

      • http://twitter.com/Forgen Sean Bell

        “I have yet to see any valid reasoning for this move.”

        I believe it is a very valid reason to drop H.264 support when that proprietary codec is costing them (and in the browser world, ONLY them) money. Sure, there may be a handful of devices that may have dedicated H.264 decoding hardware, but more likely they have more generalized hardware video decoders that can handle MPEG-2 natively and accelerates other codecs on top of that base hardware capability. (I recently read this described on the Qualcomm Snapdragon processor capability list. The snapdragon is used on my Android phone).