Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: Google Forks WebKit As Blink Rendering Engine

  1. #1
    Join Date
    Jan 2007
    Posts
    14,809

    Default Google Forks WebKit As Blink Rendering Engine

    Phoronix: Google Forks WebKit As Blink Rendering Engine

    Just earlier today was word that Mozilla is developing Servo, a new web-browser engine, and now comes a similar action out of Google. The search giant announced this afternoon they are forking the WebKit code-base for their Chrome/Chromium web-browser to form the "Blink" engine...

    http://www.phoronix.com/vr.php?view=MTM0MjM

  2. #2
    Join Date
    Oct 2012
    Location
    Cologne, Germany
    Posts
    308

    Red face Cool!

    This definitely is interesting news!
    I look forward to a rendering-engine with less legacy-bloat of the old days having been mainly with Apple and Safari. There is no need to refer to how big of a step it was to remove the old Apple-style-span.

    In this regard, getting rid of 4.8 million lines of more or less relevant code (I guess rather the latter, being architecture-specific) will have its merits.
    Last edited by frign; 04-03-2013 at 06:40 PM.

  3. #3
    Join Date
    Mar 2013
    Posts
    65

    Default

    Opera will be contributing to Blink as well (source).

  4. #4
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,891

    Default

    What the fsck did they cut!? 4.5Million lines of Code? Jesus H Christ o.o

  5. #5
    Join Date
    Nov 2012
    Posts
    165

    Default

    Quote Originally Posted by Ericg View Post
    What the fsck did they cut!? 4.5Million lines of Code? Jesus H Christ o.o
    It is not actually 4.5 million lines of code or 7000 files of code, WebKit is nowhere near that big. They are counting the deleted test-results for other ports. The layout-test and tests-result make up around 95% or all data in the webkit repository.

  6. #6
    Join Date
    Feb 2011
    Posts
    1,127

    Default

    So it's a fork of a fork. I wonder if Apple is going to complain about how bad forks are.
    Last edited by TheBlackCat; 04-03-2013 at 07:59 PM.

  7. #7
    Join Date
    Sep 2011
    Posts
    688

    Default

    Quote Originally Posted by frign View Post
    There is no need to refer to how big of a step it was to remove the old Apple-style-span.
    Glad it is dead, this made me ban Safari as a web browser in an all Mac environment because of how badly it behaved with WYSIWYG. Back then Safari also had a tendency to crash when undoing or just randomly.

  8. #8
    Join Date
    Apr 2012
    Posts
    51

    Default prefix?

    So now we need to use a -blink- prefix and the -webkit- prefix with all CSS3 "statements"? Or what will happen?

  9. #9
    Join Date
    Jul 2010
    Posts
    449

    Default no prefixes

    They aren't going to have a prefix. If something's not ready then they're going to hide it behind an "enable experimental features" button, but it will always use the non-prefixed form.

  10. #10
    Join Date
    Apr 2012
    Posts
    51

    Default

    Quote Originally Posted by archibald View Post
    They aren't going to have a prefix. If something's not ready then they're going to hide it behind an "enable experimental features" button, but it will always use the non-prefixed form.
    Sounds good . Thanks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •