Guess who is WebKit's new best friend

11 thoughts on “Guess who is WebKit's new best friend”

      1. Om, not only do you misrepresent WebKit, but now it sounds like you also don’t know what KDE is…

        For the record, KHTML originated from KDE (not a variant of Linux), but it wasn’t compatible enough for anyone to use over Mozilla Firefox.

        Apple, in need of a browser, chose KHTML as a starting point for their WebKit (___Kit is the standard nomenclature for many of Apple’s frameworks). In the process they fixed a lot of bugs and divorce it from the dependencies on Qt, but presumably this was preferable to adapting the heavyweight Mozilla code.

    1. Webkit was Apple’s fork of KDE project’s KHTML efforts. In the beginning, they weren’t a good member in the KHTML community. Eventually, the Apple agreed to open up Webkit development, and the KDE folks agreed to make Apple’s fork the official branch, or something like that.

  1. The flexibility of HTML vs the convenience of apps is not going to be an easy fight for the browser. Also, apps live in an ecosystem with a sound biz model around them. That said, the cloud could become relevant for the mobile internet as well. But the cloud faces big hurdles from both Apple and Google (and probably Windows as well), so unless something earth shattering happens, the browser is not unlike the swiss-army knife in your travel pouch whereas you use a bunch of regular knives and various tools(apps) in your daily life.

This site uses Akismet to reduce spam. Learn how your comment data is processed.