Linked by Thom Holwerda on Wed 3rd Apr 2013 22:27 UTC
Google It's apparently browser engine day today. After Mozilla and Samsung announcing Servo, Google has just announced it's forking WebKit into Blink. Like WebKit, Blink will be open source, and it will also be used by other browser makers - most prominently, Opera has already announced it's not using WebKit, but Blink. Update: Courtesy of MacRumors, this graph illustrates how just how much Google contributed to WebKit. Much more than I thought. Also, Chrome developer Alex Russell: "To make a better platform faster, you must be able to iterate faster. Steps away from that are steps away from a better platform. Today's WebKit defeats that imperative in ways large and small. It's not anybody's fault, but it does need to change. And changing it will allow us to iterate faster, working through the annealing process that takes a good idea from drawing board to API to refined feature."
Thread beginning with comment 557625
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by vtolkov
by Nelson on Thu 4th Apr 2013 16:58 UTC in reply to "RE[3]: Comment by vtolkov"
Nelson
Member since:
2005-11-29

Thats nice and pie in the sky and all, but its not what happens in practice.

The W3C throws a wrench in all of this with their lethargic standard setting process.

WebKit is a wild beast from version to verson, browser to browser. Its basically a "Browser stack" where vendors choose shelf made components, substitute others (v8 instead of JSC) and generally this leads to a bunch of incompatible implementations with varying degree of standard support.

We had one IE6. We have a ton of WebKit splinters running on various mobile devices, some having varying syntaxes for the same feature and others being so chocked up on vendor prefixes that its not really the web anymore.

This isn't WebKit's fault per say, and other browsers suffer from this to an extent -- its just the most prominent example.

What web standards needs is a more nimble process that doesn't take ten years per standard.

Reply Parent Score: 3

RE[5]: Comment by vtolkov
by Radio on Fri 5th Apr 2013 13:17 in reply to "RE[4]: Comment by vtolkov"
Radio Member since:
2009-06-20

The W3C throws a wrench in all of this with their lethargic standard setting process.

The W3C is sabotaged by infighting between vendors. Fix the W3C, instead of sneaking in a "de facto" standard.

Reply Parent Score: 3