1/7/2024 0 Comments Webkit vs blinkOne example of something Google would like to do is assign different sections of Web pages called iframes to various computing processes. And because that's such a foundational part of the software, not some high-level module tacked onto the core, it's really hard to accommodate multiple approaches, he said. "Chromium has a very different multiprocess architecture than the other WebKit-based browsers," said Alex Komoroske, product manager for Google's Open Web Platform team. One major example of how the Apple and Google WebKit projects have diverged involves how the browsers divide up computing processes running in parallel. Technical differences: Multiprocess design There never has been a single WebKit agenda for Apple and Google, and social tensions persisted as the two groups tried to work together. It's not just technical matters that led to the split, though. Google used WebKit to give its browser a running start, but now Chrome is mature enough to stand on its own. WebKit is a browser engine, software with the job of processing Web pages' instructions and rendering the result on a computing device's screen. It follows the pattern of Google naming projects after what it deems relics from the past: Chrome is designed to minimize user-interface "chrome" that surrounds Web pages the Chromebook Pixel's high-resolution screen is designed to make pixels disappear and Blink is designed to do away with browser engine irritations. The Blink name is a reference to the despised and now extinct blink tag of early HTML that made text blink off and on. Opera Software, which scrapped its own Presto engine and adopted Google's Chromium version of WebKit, will use and contribute to Blink, according to Opera Web evangelist Bruce Lawson. "We're confident this will allow us to move faster and allow the rest of the WebKit community to move faster, which ultimately will allow the Web to move faster," Upson said.Īpple declined to comment for this story. The pains of forking WebKit into Blink are worth it, argued Linus Upson, the Google vice president of engineering for Chrome. Major "forks" in open-source projects can be divisive and bitter, though a certain collegiality among Web programmers seems likely to forestall that negative outcome in the case of Blink. With Blink, each company will go its own way, working separately to add new features and to support new Web standards rather than being able to capitalize on the other's work. WebKit is an open-source project, meaning that anyone can use and modify the software, but previously Google and Apple were all contributing to the same code base. The move marks the end of years of direct WebKit programming cooperation between the two rivals. Initially it uses the same software code base that all WebKit-based browsers share, but over time it will diverge into a totally separate project, Google announced today. In a move that Google says will technologically liberate both Chrome and Safari, the company has begun its own offshoot of the WebKit browser engine project called Blink. A years-long marriage of convenience that linked Google and Apple browser technologies is ending in divorce.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |