Tuesday, September 22, 2009

Why Google Chrome Frame won't help

So Google just announced a new open source project: Chrome Frame.
Google Chrome Frame is an early-stage open source plug-in that seamlessly brings Google Chrome's open web technologies and speedy JavaScript engine to Internet Explorer. With Google Chrome Frame, you can:
  • Start using open web technologies - like the HTML5 canvas tag - right away, even technologies that aren't yet supported in Internet Explorer 6, 7, or 8.
  • Take advantage of JavaScript performance improvements to make your apps faster and more responsive.

Just to clarify: I don't think it hurts anything, and I applaud Google's intentions to rid us all of supporting such a piece of shit like IE. It looks like a cool piece of technology and the most creative effort I've seen since the Mozilla ActiveX control.

But it'll do jack shit to get around supporting IE in all of its broken glory.

I'll ignore the current requirement of adding a meta tag to a page in order to trigger the plugin, and also the fact that this extremely young and experimental project doesn't have things like deployment tools for IT departments to use. They just announced this, and want feedback from developers at this point so they can continue working on it.

Google Chrome Frame will do jack shit, because the stick-in-the-mud companies that can't part with IE6 won't install a browser in a plugin. If the companies didn't have ignorant, self-defeating, head-up-their-fucking-ass rules about what level of corporate hell they'll ban you to for trying to install something on your machine, they would simply let you install the browser itself. None of the companies currently threatening their employees with fines or even firing will consider for a second adding an entire browser via a plugin. Employees might try to install it on their own in order to try to hide the fact that they get more work done when not using a complete piece of shit, but that will just prompt more companies to learn how to block people from installing browser plugins.

One of the reasons even the more laid back companies would probably let people install a whole other browser before installing a browser in a plugin: support. If you have employees using web applications that take advantage of Chrome Frame and they hit a bug either in the web application itself or something more severe like a browser crash (or maybe the always entertaining BSOD), that will fucking suck to figure out what happened. And if you installed Chrome Frame without their knowing, then call up support with a "my browser fucking crashed on me again" that turns out to stem from Google's crap code, your employer will fuck you. Shit, once they finally upgrade to IE8 they'll have enough of a problem with browser engines.

We instead need to find out what products companies use that require IE and either get the distributer to stop that shit, or provide alternatives. This will take a fucking long time, so I expect we'll also need to educate some of these dumbasses who think that they'll stay more secure by using an ancient fucking version of the least secure browser in existence, so they'll at least let one of the better choices onto the machines. Then employees will still have IE6 for the ten-year old shit software that requires it, and something else to use that actually works with the rest of the world.

Labels: , , , , ,


Blogger Unknown said...

MS haters are so naive and fun.
You speak about "web standards", yet how many HUNDREDS of validation errors does your own blow have?


11:17 AM  
Blogger The Hater said...

Алексей Волков: I bet it fails validation. If you check the source, I haven't bothered to fix the Blogger template, so it uses the crap Google vomits out by default. I'd rather spend what little time I have on the content and discussion itself.

10:49 AM  
Blogger pieroxy said...

The best thing is to use the IE awareness initiative on your websites. We need to get rid of this browser (specially old versions) as soon as possible.

2:28 AM  
Anonymous Tai said...

As a web designer I don't support IE6. My clients can either pay me extra to create a conditional stylesheet or, what I suggest, I can put IE6 NO MORE script on to their websites to encourage users to upgrade.
Check it out:

4:42 PM  
Anonymous Anonymous said...

There is also another script for embedding in a website.
And it really looks like Internet Explorer error messages.

9:58 PM  
Anonymous Anonymous said...

This comment has been removed by a blog administrator.

1:06 PM  
Blogger Kevski said...

Sharepoint. IE. Sheer bloody hell.

5:04 AM  
Anonymous Anonymous said...

lowkey speaking:

Алексей Волков you sound like someone hired by microsoft. Or you are working for them/ partnering with them in some way. If not, i simply can't comprehend your standpoint...

No one working with web design/development can in their right mind prefer IE over other browsers. I am no fanboy, i am a realist, countless times i have seen my designs and code following strict standards be destroyed by IE for no apparent reason.

You are a "hater" if you hate for personal reasons. Not when point out fucking obvious flaws and the fact that that Microsoft, has set back web development years! Speaking from personal experience microsoft and IE are huge problems for the webdevelopment community, and always requires extra time, because they via they monopoly tries to forces their own standards down the rest of the worlds throat...

f*ck microsoft
f*ck ie

9:43 AM  
Blogger Joel said...

I hate IE, but version 8 is a huge fucking step up from the previous bullshit versions. At least they're trying to not suck.

Still won't ever use it, save for downloading chrome and firefox on a reinstall or something like that.

The EU had the right idea by forcing MS to include options. I was really hoping they would do the same for the US release


4:31 AM  

Post a Comment

<< Home