Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Chromium Google Opera Safari The Internet Apple

WebKit Developers Discuss Removal of Google-Specific Code 92

hypnosec writes "WebKit developers have already started discussing the removal of Chrome- and Chromium-specific code from the rendering engine in a bid to make the code easier to maintain. Just a couple of days back, Google announced it will go ahead with a WebKit fork to develop a new browser engine — Blink. According to Google, having multiple rendering engines — just like multiple browsers — will allow for innovation as well as contribute toward a healthy open-web ecosystem. The discussion was started by Geoffery Garen, an Apple WebKit developer. He said Google's departure is an 'opportunity to streamline' the code of WebKit, which would eventually make development 'easier and more coherent for everyone.' Garen expects that developers who will be working on WebKit in the future should help to clean up the code. However, Adam Barth and Eric Seidel — two Google WebKit developers — have already offered their help." Google plans on making the switch to Blink in the stable Chrome release in around 10 weeks. They've posted a half-hour video explaining how the transition will work.
This discussion has been archived. No new comments can be posted.

WebKit Developers Discuss Removal of Google-Specific Code

Comments Filter:
  • by Anonymous Coward on Friday April 05, 2013 @09:25AM (#43367605)

    See my subject-line, & since Chrome-based browsers aren't 64-bit in Windows, then once the Blink/WebKit builds of Opera release (Presto = gone, what a shame imo), odds are they too will ONLY be 32-bit (that is, IF "Chrome/Chromium" & browsers derived for it for Windows are ANY kind of "indicator" here)...

    * :(

    (Afaik @ least? Chrome/Chromium are only 32-bit for Windows, & hence, my statements above...)


    P.S.=> Got to thinking about this today, & just had to note/mention it (unless anyone else KNOWS otherwise that is, & I'd appreciate that IF anyone does)...

    ... apk

  • Re:quid pro quo (Score:5, Informative)

    by moronoxyd ( 1000371 ) on Friday April 05, 2013 @09:50AM (#43367793)

    For the same reason there is Apple specific code in WebKit. And (probably) PowerPC code, and x86 code, and Android code, and iOS code, and ...

    Why is HyperV code in the Linux kernel?
    Or code that is for Intel graphics?

    If a piece of software tries to support many platforms and usage cases, you have code that is only used in specific scenarios.

    And if the reason to support this platform or usage case is gone (i.e. iOS support for Blink, and Google support for post-split WebKit), then you remove it.

  • Re:Clean It Up Boys (Score:4, Informative)

    by BasilBrush ( 643681 ) on Friday April 05, 2013 @01:33PM (#43370099)

    Webkit does have a JavaScript Engine. It's called JavaScriptCore. But Chrome didn't use it.

Exceptions prove the rule, and wreck the budget. -- Miller