Google Forking WebKit to Create New Web Rendering Engine for Chrome

Discussion in 'MacRumors.com News Discussion' started by MacRumors, Apr 3, 2013.

  1. macrumors bot

    MacRumors

    Joined:
    Apr 12, 2001
    #1
    [​IMG]


    Google announced today that the company is forking the WebKit rendering engine to create its own web rendering engine called 'Blink'. Google had been the using Apple-initiated WebKit project to power its Chrome web browser. Future versions, however, will now be based on this new system.

    Google is now free to make changes to its rendering engine with less complexity and bureaucracy than when it was saving its changes to Webkit. The company posted this on its FAQ explaining why it wanted to create a new engine:
    With the change, Google has set Chrome and Apple's Safari on their own paths. Webkit was originally created by Apple as a fork to the KHTML rendering engine. Apple took interest in developing it when launching Safari for the Mac, and it now powers Safari for iOS, as well.

    WebKit has been heavily adopted with over 20 companies now contributing to the project. Google and Apple, however, have remained the most active contributors to the open-source project.

    [​IMG]
    In fact, Google has been the most active contributor of WebKit in the recent years. This graph from Bitergia (above) shows Google's increasing number of "commits" to WebKit over the years. Google's efforts will now be directed at 'Blink'. Apple has made no public comments about the news.

    Article Link: Google Forking WebKit to Create New Web Rendering Engine for Chrome
     
  2. macrumors newbie

    Joined:
    May 9, 2012
    #2
    It was only a matter of time.
     
  3. macrumors 601

    Chaszmyr

    Joined:
    Aug 9, 2002
    #3
    So much for the golden age of web standards.
     
  4. macrumors 68020

    Joined:
    Jul 8, 2006
    Location:
    California
    #4
    Doesn't matter to me, I'll just keep using Safari on my Apple products.
     
  5. Editor emeritus

    longofest

    Joined:
    Jul 10, 2003
    Location:
    Falls Church, VA
    #5
    It will be interesting to see how many folks follow Google and jump ship to support the new fork or stick with Apple and Webkit.

    It was nice to have two major companies on the same core engine for as long as it lasted.
     
  6. macrumors 6502

    Joined:
    Nov 2, 2010
    #6
    I may just have to switch back to Safari as my main browser.
     
  7. macrumors 68000

    alksion

    Joined:
    Sep 10, 2010
    Location:
    Los Angeles County
    #7
    With Opera adopting Webkit recently, I figured this would be the new standard that would minimize the fragmentation.

    I guess Google wants to keep things similar to their Android OS ;)
     
  8. macrumors 6502

    Joined:
    Apr 26, 2011
    #8
    well then...FORK YOU.
     
  9. macrumors 68020

    gmanist1000

    Joined:
    Sep 22, 2009
    #9
    You don't want to give it a chance?
     
  10. macrumors 6502a

    Joined:
    Jul 12, 2010
    Location:
    Ireland
    #10
    Opera is adopting Blink not Webkit it seems.

    http://www.brucelawson.co.uk/2013/hello-blink/
     
  11. macrumors 603

    Warbrain

    Joined:
    Jun 28, 2004
    Location:
    Chicago, IL
    #11
    Perfect, this allows Google to implement their own codecs and create their own IE disaster.
     
  12. macrumors member

    Joined:
    Mar 21, 2013
    Location:
    Baltimore
    #12
    I am really not happy about this. But lets see how this goes.
     
  13. macrumors 68040

    Bubba Satori

    Joined:
    Feb 15, 2008
    Location:
    B'ham
    #13
    Will that be different than the Safari disaster?
     
  14. macrumors regular

    sailmac

    Joined:
    Jan 15, 2008
    #14
    It's a trap!
     
  15. macrumors 68020

    Joined:
    Dec 13, 2012
    Location:
    Southern California
    #15
    This is a good move on Google's part. It will bring enhanced, richer results to all. The mentality at Google is improve, improve, improve. While certainly not perfect, I give them credit for a positive attitude and willingness to take risks.
     
  16. macrumors G4

    daneoni

    Joined:
    Mar 24, 2006
    #16
    First WebM now this.

    Isn't Safari a Webkit and H.264 browser? how is that a disaster?
     
  17. macrumors 6502

    Joined:
    Mar 1, 2003
    #17
    This might be more meaningful if Samsung weren't moving towards Rust (Mozilla's next generation rendering engine). At this point Samsung's decisions have a bigger impact on the mobile browser market than Google's decisions.

    I guess it will eventually impact Chrome for Desktop though, for whatever that's worth.
     
  18. macrumors 6502a

    Joined:
    Jul 15, 2012
    #18
    Sounds like another attempt by Google to control the keys to the Internet using open source as a veil to their true intentions. It reminds me of when they tried to hijack the video standard with WebM.
     
  19. macrumors 603

    Michaelgtrusa

    Joined:
    Oct 13, 2008
    Location:
    Everywhere And Nowhere
    #19
    Id had to happen.
     
  20. macrumors G5

    nagromme

    Joined:
    May 2, 2002
    #20
    As a bizarre consequence of this, will Apple once again have a reason to make Safari for Windows?

    Agreed. Google has a laser focus on serving their customers better and better: advertisers eager to pay for personal data. (What's Google's default setting for Do Not Track?)
     
  21. macrumors regular

    Joined:
    Feb 17, 2007
    #21
    Justo be clear, the article states that Rust is the programming language that the new engine dubbed 'Servo' is being written in
     
  22. macrumors G5

    Joined:
    Jun 22, 2009
    #22
    If Google was a very active participant in WebKit over the years - while some may scoff at Google going in their own direction and wish them ill on their endeavor or mock them. Consider that WebKit won't benefit from their tweaking any more.

    Things will get interesting.
     
  23. macrumors 65816

    japanime

    Joined:
    Feb 27, 2006
    Location:
    Japan
    #23
    If it results in even an even more seamless integration with Google's various web-based services, then this could be a very good thing.
     
  24. macrumors regular

    Joined:
    Feb 17, 2007
    #24
    This! I wonder if we'll have another webM debacle?
     
  25. macrumors G3

    Renzatic

    #25
    I always thought WebM was an honest but ultimately vain attempt to get away from MPEG LA.
     

Share This Page