I Don’t Support a WebKit Monoculture Deux

Things in the internet space are weird.

First you have a guy telling that he would support a monopoly in the browser market (which I fully raged against). And then, out of nowhere, one of the jQuery guys come out and tell everyone that they are tired of doing hacks to avoid WebKit bugs — which finally sparked the Chrome/WebKit team to fix said bugs, which was even celebrated by John Resig himself.

But the thing is: Ok, the WebKit team fixes the bugs. Does that mean that they can simply remove said hacks?

The answer is a loud “no”. Because WebKit is not a single browser; it’s four, with a fifth coming around. Chrome, Chromium, Safari for OS X, Safari for iOS and, soon enough, Opera (and we still need to see how many versions of it will appear — although I believe that there will be at least a desktop version and a mobile version).

If tomorrow the Chromium team releases a WebKit version with all the fixes, will my Safaris (iOS and OS X) finally be updated? I don’t think I need to answer this, right? This just proves how “not smart” (to play nicely) the “WebKit monoculture guy” is: The fact that it’s being support by two different companies, with two different release timelines, is actually creating a fragmentation of the WebKit market (something that you should be used to if you use any Google tool, apparently).

I’m not a full time hater of everything WebKit. Firefox got a lot better since Chrome showed up, but the fact that some many people are brown-nosing it is simply sad. Chrome had some good ideas, but it’s far from being the “awesome browser to rule them all” like everybody is claiming.