Google going its own way, forking WebKit rendering engine

A number of people were complaining about how not enough common implementations on the web was a bad thing; and how everyone using webkit would lead to complacency. Google forking webkit to make it its own might be just enough to keep them all different enough to keep standards going :)

Re: Google going its own way, forking WebKit rendering engine

#7

Post by mikewest » Wed, Apr 03, 2013, 9:31 PM UTC

msoad wrote: post #4

My understanding is that Dart VM will be in Chrome soon.

http://www.chromium.org/blink#new-features has some detail about how we plan to add features to the platform. We're certainly hoping to be pretty transparent about how things get into Chromium.

Re: Google going its own way, forking WebKit rendering engine

#8

Post by stdbrouw » Wed, Apr 03, 2013, 9:32 PM UTC

[deleted] wrote: post #3

[deleted]

Too bad it's not relevant to the situation.

Re: Google going its own way, forking WebKit rendering engine

#9

Post by doe88 » Wed, Apr 03, 2013, 9:37 PM UTC

> Google also argues that the decision will introduce greater diversity into the browser ecosystem and might mitigate concerns that the mobile Web in particular was becoming a WebKit monoculture.

Ahah so much hypocrisy condensed in this sentence. Yeah it's constraining to share code and have compile time #defines but if every vendor did the same there wouldn't be any common project.

Re: Google going its own way, forking WebKit rendering engine

#10

Post by cnlwsu » Wed, Apr 03, 2013, 9:41 PM UTC

nugget at the end: "there won't be any -blink or -chrome CSS prefixes; like Mozilla, all new experimental features will require developers to enable them in the browser's options page"