Opera, Google Chrome Browsers to Jump Off WebKit Onto "Blink" Branch
April 4, 2013 1:38 PM
comment(s) - last by
(Source: Marvel Comics)
Apple will likely be left on its lonesome supporting WebKit
For a long while now WebKit (derived from KHTML) has been marching towards being the dominant rendering engine of the web. Competing against Microsoft Corp.'s (
) proprietary Trident engine and the
's open-source Gecko engine, WebKit powers a number of browsers.
Google, Inc.'s (
) Chrome, Apple, Inc.'s (
) Safari, and BlackBerry Ltd.'s (
) device browsers all use WebKit. And with Norwegian browser-maker Opera Software ASA's (
) decision to
ditch its proprietary Presto engine
and saddle up with WebKit, it seemed WebKit was headed towards hegemony.
I. Google -- Do Blink
But today Google shook up the browser tree, announcing that it would be branching Chromium's rendering engine off of WebKit. The new engine will be dubbed "Blink". What's more Opera has already announced that it will be joining the new effort.
Apple appears unlikely to make the switch. It's unclear whether BlackBerry will.
Google says its main reason for jumping to a new branch is because it uses a more complex multi-process model than Apple -- the other biggest WebKit contributor. Google's Adam Barth
Chromium uses a different
than other WebKit-based browsers, and supporting multiple architectures over the years has led to increasing complexity for both the WebKit and Chromium projects. This has slowed down the collective pace of innovation.
Chromium is a little complex multi-process-wise. [Image Source: Google]
The change won't happen overnight, but the jump means that the engine behind Chrome (Blink) and WebKit will gradually drift apart.
II. Practicality or a Competitive Maneuver?
Alex Russell, another Google Chrome engineer, reemphasizes this point, predicting that coverage on Blink will be full of "tripe we’re about to sell each other as 'news.'" He writes that the two major drivers of the switch were development time and processing speed. He
Why couldn’t those cycle-time-improving changes happen inside WebKit? After all, much work has happened in the past 4 years (often by Googlers) to improve the directness of WebKit work: EWS bots, better code review flow, improved scripts and tools for managing checkins, the commit queue itself. The results have been impressive and have enabled huge growth and adoption by porters. WebKit now supports multiple multi-process architecture designs, something like a half-dozen network stack plug-ins, and similar diversity at every point where the engine calls back to outside systems for low-level implementation (GPU, network, storage, databases, fonts…you name it). The community is now committed to enabling porters, and due to WebKit’s low-ish level of abstraction each new port raises the tax paid by every other port.
has observed, this diversity creates an ongoing drag when the dependencies are intertwined with core APIs in such a way that they can bite you every time you go to make a change. The
Content API boundary
is Blink’s higher-level “embedding” layer and encapsulates all of those concerns, enabling much cleaner lines of sight through the codebase and the removal of abstractions that seek only to triangulate between opaque constraints of other’s port.
In other words, aside from the process model, another place where Apple and Google's objectives differ is platform support. Google supports many platforms -- Apple supports only one. Google wants to go back to the drawing board and better encapsulate the platform implementations to prevent them from slowing the overall engine.
Google is leaving Apple on its lonesome to develop WebKit. [Image Source: Google]
But as much as Mr. Russell emphasizes practical necessities, there is one implication that's at least an interesting coincidence, to say the least: Google branching away from the core WebKit is a major blow to Apple.
For some time now Apple could rely on Google to make WebKit as fast and reliable as possible. Apple, thus, effectively gained a better Safari for Macs and i-devices thanks, in part, to Google's labors. Now it will have to go it alone.
Google may say the move is mere practicality -- and it certain does offer a strong justification in support of that claim. But the branch is yet one more instance of how Google and Apple --
once close allies
relationship becomes increasingly adversarial
Infrequently [Google Chrome Engineer]
This article is over a month old, voting and posting comments is disabled
4/5/2013 12:16:42 AM
Both are bad. Used to be pretty good. Now FireFox is way better with smaller memory footprint and faster. Chrome became bloated and hogging resources like crazy yet, not that fast. Google needs to get back to their roots and make things "lean and mean" nto adding a ton of features that spoils the browser. Until I can see that improvement, Firefox remains king!.
4/5/2013 5:32:00 AM
Chrome is still about twice as fast in Peacekeeper. But I agree is seems to do better with memory management. Oh and it annoys the hell out of me that I still cannot choose the installation folder for Chrome - it's hidden somewhere in AppData and it's quite shocking to see it using >300MB.
4/5/2013 9:31:05 AM
If you download the "offline installer" for all users, it will install to program files.
The idea of appdata being its install location for default web installations is the same concept behind a virus planting itself in your appdata folder. It doesn't need admin rights to go there. So even a person locked down from installing apps to programfiles can usually install chrome under their user profile. It also doesn't need admin rights to update itself. When in program files, you do need admin rights to put files there.
"When an individual makes a copy of a song for himself, I suppose we can say he stole a song." -- Sony BMG attorney Jennifer Pariser
Opera Saddles up With Google, Apple by Moving to WebKit
February 13, 2013, 2:54 PM
Report: Google Pays $700M to Apple for Prominent Mobile Search Placement
February 11, 2013, 2:48 PM
Google CEO: We Have no Real "Competitors", Apple's Fixation is Self-Destructive
December 11, 2012, 4:45 PM
Apple Continues Its “Google Cleansing” by Removing YouTube App in iOS 6 Beta 4
August 6, 2012, 3:02 PM
Apple Adds New Password Protection for Third Party iCloud Apps
September 17, 2014, 8:50 PM
Facebook Tests Moments App, Aims to Keep Your Private Memories Private
September 17, 2014, 5:46 PM
Russian Hackers Compile List of 10+ Million Stolen Gmail, Yandex, Mailru
September 11, 2014, 11:41 AM
House Minority Leader Pelosi Criticizes FCC's "Fast-Lane" Net Neutrality Plan
September 9, 2014, 4:15 PM
Smarter Than Siri? Cortana Adds Game NFL Game Winner Prediction
September 3, 2014, 4:12 PM
Apple Says Nude Celebrity Photo Dump Wasn’t Result of iCloud, Find My iPhone Breach
September 2, 2014, 3:26 PM
Most Popular Articles
HTC Preps Nexus 9 With Nvidia K1 64-Bit "Denver" SoC, Android L Onboard
September 10, 2014, 10:21 PM
Quick Note: Buy an Xbox One Sept 7-13, Get a Free Game
September 4, 2014, 10:42 AM
Apple Announces Its Smartwatch: The $349 Apple Watch
September 9, 2014, 2:09 PM
Dell Announces "World's Thinnest" Tablet: The Venue 8 7000 Series
September 11, 2014, 8:51 AM
T-Mobile Launches Un-carrier 7.0, Beefs Up Wi-Fi Calling
September 11, 2014, 2:56 PM
Latest Blog Posts
ISIS Imposes Ban on Teaching Evolution in Iraq
Sep 17, 2014, 5:22 PM
Space Terrorism is a Looming Threat For the United States
Apr 23, 2014, 7:47 PM
Facebook Aims to Provide Internet to "Every Person in the World" with Drones, Satellites
Apr 1, 2014, 10:20 AM
Retail Mobile Sites Experience Outages in Light of Simplexity's Bankruptcy
Mar 14, 2014, 8:48 AM
Tesla vs. BMW: Who Has the Safer EV?
Feb 1, 2014, 2:56 PM
More Blog Posts
Copyright 2014 DailyTech LLC. -
Terms, Conditions & Privacy Information