Disclaimer: If you really, really, really, like WebKit? You might not like this post.
I find the internet's seeming obsession with WebKit to be one of the worst things since IE 6 became a de facto standard. It's something that irks me so much because it influences the way other browsers work. There is a -WebKit tag that's being used because the web is being coded for the quirks that exist in the WebKit rendering engine.
And yes, it has quirks.
I'm often amazed how people seem to think that WebKit is them most amazing thing since the history of amazing. There are some major problems with some of the reasoning behind it.
>WebKit isn't the fastest anymore. I don't know if it was ever the fastest at everything, but Firefox Nightly sure does beat it in some areas. IE beats it in others.
>WebKit isn't standards compliant. No, instead of making a rendering engine that conforms to standards, WebKit has slowly made the standards conform to it. That's what IE 6 did a long while back, and it isn't any better now.
>It doesn't matter if it's Open Source. There might be 10 people outside of big companies that actually look at even a small portion of the code. Google was able to find 3,500,000 lines of code that they were able to remove over the course of 6 months that didn't negatively effect the browsing experience. Just imagine how many lines of code there are in the project.
>WebKit isn't efficient with resources. It uses more RAM, and a higher percentage of most CPUs, than the competition. People complain about the use of RAM for Firefox on OS X, but Chrome and Safari both have it beat in being beastly. Then we have the mobile browsers, and the trend continues where WebKit based browsers are often sluggish because of the lower resources that are in most devices.
I find the internet's seeming obsession with WebKit to be one of the worst things since IE 6 became a de facto standard. It's something that irks me so much because it influences the way other browsers work. There is a -WebKit tag that's being used because the web is being coded for the quirks that exist in the WebKit rendering engine.
And yes, it has quirks.
I'm often amazed how people seem to think that WebKit is them most amazing thing since the history of amazing. There are some major problems with some of the reasoning behind it.
>WebKit isn't the fastest anymore. I don't know if it was ever the fastest at everything, but Firefox Nightly sure does beat it in some areas. IE beats it in others.
>WebKit isn't standards compliant. No, instead of making a rendering engine that conforms to standards, WebKit has slowly made the standards conform to it. That's what IE 6 did a long while back, and it isn't any better now.
>It doesn't matter if it's Open Source. There might be 10 people outside of big companies that actually look at even a small portion of the code. Google was able to find 3,500,000 lines of code that they were able to remove over the course of 6 months that didn't negatively effect the browsing experience. Just imagine how many lines of code there are in the project.
>WebKit isn't efficient with resources. It uses more RAM, and a higher percentage of most CPUs, than the competition. People complain about the use of RAM for Firefox on OS X, but Chrome and Safari both have it beat in being beastly. Then we have the mobile browsers, and the trend continues where WebKit based browsers are often sluggish because of the lower resources that are in most devices.