![chrome webkit chrome webkit](https://thesafety.us/images/articles/webrtc-chrome-plugin-en-4.png)
The goal was to create a faster, leaner, and more secure web browser that would allow Apple to have more control over the browsing experience, with some improvement in performance. It was created by Apple, Inc., as a fork of the KHTML browser engine used in Netscape Navigator.
#CHROME WEBKIT FULL#
Full support for the features in browser. WebKit is a rendering engine used to create web browsers such as Safari. New way of writing native applications using web technologies: HTML5, CSS3, and WebGL. Given its track record there, it makes sense for the company to take control of its own rendering engine. NW.js (previously known as node-webkit) lets you call all Node.js modules directly from DOM and enables a new way of writing applications with all Web technologies. It's done an excellent job of the V8 JavaScript engine, creating a fast, capable engine. Google, it seems, is also very good at optimizing code when it comes to browsers. And while having all that dead wood buried in the codebase might be fine on desktop and notebook systems with a beefy processor and bags of RAM, on mobile systems with limited processing power, storage, RAM and power, a more focused, streamlined rendering engine would be better for all. There's no doubt that Apple has effectively managed the project and transformed it into a capable post-PC era rendering engine, but it is clear that if Google can eliminate 4.5 million lines of code from the project, then there's a lot of dead wood in there. WebKit is long in the tooth, and is a product of PC thinking. The reason Google wants Blink is down to one thing - the post-PC era. Sure, Google is interested in adding new features, but in such a multi-platform world, the idea of filling Blink with features that are incompatible with other rendering engines is almost unimaginable. The fact that Google focused on simplifying the WebKit is telling.