Google says the split is necessary because Chrome uses a different multi-process architecture than other web browsers based on Webkit. It’s based on Webkit, but as development continues, it will likely start to look more and more different from the software it’s forked from. The company has announced plans to develop its own rendering engine called Blink. Google has been using the open source Webkit rendering engine to power its Chrome web browser and Chrome OS operating system since day one. How long will my Fire Tablet get security updates?.How to use an SD card with Amazon’s Fire tablets.How to sideload apps on Amazon Fire tablets.How to disable Amazon apps and features.Hack your Amazon Fire tablet with Fire Toolbox.How to install Google Play on the Amazon Fire HD 10 (9th-gen).How to install Google Play on the Amazon Fire HD 8 (2020). How to install Google Play on the Amazon Fire 7 (2022) with Fire OS 8.But as an Apple engineer noted at the time, KHTML was considerably less bloated and more lightweight, and Steve Jobs made a point of talking up Safari’s speed while demoing the browser at that year’s Macworld Expo.Google forks Webkit, introduces Blink rendering engine for Chrome (and Opera) - Liliputing Close Search for: Search As web designer John Allsopp notes, Apple surprised a lot of pundits by using a little-known engine called KHTML when it launched Safari in 2003, rather than basing its code on Firefox. While Flow is just a blip on the browser scene today, you never know where it might go. “For the same reason that you don’t only want to plant a single crop.” “There is something about diversity that is just inherently good,” he says. There’s no guarantee that they won’t eventually lose interest and underfund their efforts. Even with no shortage of outside input, building browser engines is an expensive, time-consuming process that tech giants such as Apple and Google are largely funding themselves. He’s argued that browser makers can focus on user-facing features, such as Brave with its focus on privacy or Vivaldi with its extreme customization, rather than behind-the-scenes rendering-engine improvements.īut as Brian Kardell, Igalia’s developer advocate, points out, a diverse browser culture still has its merits. Not being allowed to use a different browsing engine on one of the world’s biggest computing platforms could further dissuade developers from trying to make their own.Ĭhris Coyier, the cofounder of CodePen and creator of CSS-Tricks, says that due to the head start that big browsers already have, building a competitive browser engine would be a billion-dollar effort with no clear payoff. Even Mozilla, which develops its own Gecko engine for Firefox as a matter of principle, still has to use WebKit on iOS. Opera had done the same in 2013, abandoning its venerable Presto engine and adopting Chromium.Ĭompounding the matter is Apple, which requires all third-party browsers on iOS to use its own WebKit engine, ostensibly for security reasons. Microsoft famously gave up on its EdgeHTML engine a few years ago, switching to a version of Edge based on Chromium and the Blink engine in early 2020. As a result, most browser makers have backed away from building and maintaining their own engines.
0 Comments
Leave a Reply. |