Google Drops Webkit and Announces Blink, Their Own Rendering Engine

Google commits the most to webkit

Web developers and designers get ready for even more browser fragmentation, because you’re in for a ride! Google announced today they are breaking ties with Apple’s open source Webkit rendering engine to retrofit the web with their rendering engine called Blink.

There are many contributors to the Webkit engine other than Apple and Google which include Samsung, BlackBerry, Opera, Amazon to name a few who will most likely need to make a decision which bed their going to want to sleep in moving forward as well.

Microsoft isn’t one of those contributors, because they operate with their own rendering engine MSHTML meanwhile Mozilla’s C++ rendering engine Gecko originates from Netscape Navigator days. So, they won’t need to make any changes clearly.

An example the new Blink engine would contribute to the web community includes improving iframe support for various computing processes.

“It would be great for security and stability and performance if we could have iframes embedded in pages be a separate process,” Alex Komoroske - Product Manager, Chrome said. “But it would require a lot of change that would really disrupt the rest of the WebKit community.”

Change usually comes with resistance especially from a community that struggles to build  one website for dozens of different browsers only to pray their audiences use either webkit or gecko or at the very least IE9 instead of IE7/IE8 and don’t even touch my site with IE6!

“It’s our belief that having multiple rendering engines will spur innovation,” Komoroske said. “In the long term, we’re increasing our commitment to standards.”

We were so close to have practically a standard rending engine with many of the big players even Opera, which only recently announced they planned to drop its Presto engine for WebKit, but just now said they will back Google’s initiative.

There won’t be much of a difference with Blink for web developers in the mean time as Google plans to work on “internal architectural improvements and a simplification of the codebase”, which the company said it will initially remove 7 build systems and cull of over 7,000 files to yield a “healthier codebase” with less bugs.

CNET has a great article on the matter, which you should read up if you’re interested to learn more.

About Evan Moore

Hi - Thanks for visiting my post! I'm a guest contributor at Phillihp's Tech Blog and I'm avid tech enthusiast about web, mobile or basically anything technology driven. If it's got a computer chip in it, i'll pretty much talk about it. I was recently called an "idea man", hopefully that's a good thing, but as the label suggested, I have a lot of them and I'm always looking for more! Hope to hear from you!
This entry was posted in *, Browsers, Chrome, Google, News, Safari. Bookmark the permalink.

2 Responses to Google Drops Webkit and Announces Blink, Their Own Rendering Engine

  1. Oh, great subject! I like this.

Add Comment Register



Leave a Reply

Your email address will not be published. Required fields are marked *

ERROR: si-captcha.php plugin says GD image support not detected in PHP!

Contact your web host and ask them why GD image support is not enabled for PHP.

ERROR: si-captcha.php plugin says imagepng function not detected in PHP!

Contact your web host and ask them why imagepng function is not enabled for PHP.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>