Mobile Zone is brought to you in partnership with:

Robert has been working with web developing, mostly interface coding, since 1998. His biggest interests lies in HTML, CSS and JavaScript, where especially JavaScript has been a love for quite some time. He regularly blogs at http://www.robertnyman.com about web developing, and is running/partaking in a number of open source projects (http://code.google.com/u/robnyman/). Robert is a DZone MVB and is not an employee of DZone and has posted 57 posts at DZone. You can read more from them at their website. View Full User Profile

Thoughts On Blink, Google’s New Rendering Engine

04.05.2013
| 6167 views |
  • submit to reddit

Yesterday, Google announced that they’re moving from the WebKit rendering engine to their own, named Blink, for Chromium (and thus all Google products based on WebKit).

What Is Blink?

Blink is a rendering engine based on WebKit. For now, it will be very similar to what WebKit is, but as it develops over time, I’m sure we will see a number of differences.

One good thing to notice – as outlined in their Developer FAQ on Blink – is that they won’t be adding any new prefixes, like -blink-border-radius etc.

Instead, they’ve chosen the same approach as Mozilla, to instead have developers enable new experimental features in about:flags in Google Chrome. They will, however, support already implemented -webkit prefixes.

What It Means

It means we’re getting a new rendering engine, thus contributing to the needed diversity I talked about in The WebKit culture & web rendering engine diversity.

It’s a fairly logical move to me, and as Rob Hawkes and I outlined in WebKit: An Objective View, WebKit and the options and differences are much bigger than most people seem to think.

Google is a business. They aim to be as streamlined and flexible as possible, and this is their way of doing that. I don’t have a problem with that, and I hope it leads to more healthy competition in the web browser rendering engine space.

It also means that all those people saying that WebKit was good for everything when Opera switched to it, defending it as the only rendering engine that mattered were, well, not entirely correct…

I also hope, and believe, there will be less voices suggesting that Internet Explorer and Firefox switch to WebKit as well, and understand that different companies have differences approaches.

Finally, it will change the mindset of many web developers who have put an equal sign between WebKit and Web, and especially the mobile web as that. This is good.

WebKit != Web != Mobile Web

but rather

[All rendering engines] == Web == Mobile Web

What Does This Mean For WebKit’s Future?

I think this is by far the most interesting implication.

It’s a big shift for WebKit development, with Google currently having the top number of reviewers. That Apple will need to evaluate their role in WebKit, and what time and efforts they will put in, or any potential changes to make.

I also wonder if the result could be that Safari will fall behind other web browsers with far less contributors?

I think, long-term, it will definitely affect iOS and the web browsing experience in general, and I also wonder if other parties using WebKit now will consider Blink. And where contributor loyalty will be.

The web is indeed an exciting sector to be in!

Published at DZone with permission of Robert Nyman, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)