Why All Browsers Should Move to WebKit

Published in: Browsers, Opera, Rant

As a web developer, I know the pains of trying to work around kinks to support all variations of all major browsers to have a unified look, feel, and performance. Even though today the top browsers do a better job at supporting and implementing new web-standards it’s far from a perfect situation. So when I heard Opera was switching its rendering engine to WebKit, a first major browser to do so among many other Opera firsts, I was excited because it means I will have one less browser to test for mundanely simple things that all browser should have by default, and do a good job at it.

Why do all browsers have such varied levels of performance in implementing web standards?

If you want a single example on pitfalls of having too many options, web rendering engines would be the perfect candidate.


Yes, there are valid reasons to worry about having a single choice for the rendering engine. That it might make web-standards less important. That the power might shift to rendering engine as opposed to web standards. But, WebKit is open source and there already exists many forks of it. Think of WebKit as a Linux kernel and Browsers, using WebKit, as Linux Distributions. You can use the same Kernel/WebKit but your performance and feature will and can wildly vary depending on your implementation. There is a reason why people stick with a certain distribution, even though the underlying infrastructure is the same/similar the result and experience can be wildly different. Centos and Ubuntu may use the same kernel and still provide a wildly different level of user experience.

I rather deal with several forks of WebKit, than deal with different rendering engines. In the end, only the browser with the best user experience will win the race. As we have seen with Firefox and now with Chrome.

about | twitter | facebook | archive | rss