It has a link to this post http://blogs.kde.org/node/1001 from 2005 saying there isn't much hope.
It would be nice to have a 2013 update.
There was a huge amount of excitement at the announcement that Safari would be using KHTML. At that time, it was almost a given that the OSS rendering engine was Gecko. KHTML was KDE's little engine that could. But nobody ever expected it to be picked up by other folks. One of the original parts of the KHTML-to-OS X port was KWQ (pronounced, "quack") that abstracted out the KDE API portions that were used in KHTML.
Folks were pretty ecstatic at first. It seemed very validating.
But that changed quickly. As Zack's post indicates, WebKit became a thing of unmergable code-drops. Even inside of the KDE community there became a split between the KHTML purists and the WebKit faction. They'd previously more or less all been KHTML developers, but post-WebKit there was something of a pragmatists vs. idealists split. Zack fell on the latter side of that (for understandable reasons: there was an existing community project, with its own set of values, and that was hijacked to a large extent by WebKit).
A few years later WebKit transformed itself into a more or less valid open source project (see webkit.org), but that didn't close the rift in the KDE community between the two, at that point rather divergent, rendering engines. There's still some remaining melancholy that stems from that initial hope and what could have potentially been, but wasn't.
It's hard to argue that WebKit being open source has been a bad thing -- in fact, I don't believe that in the slightest. But I can also understand that it's pretty head-turning to have have a project transform in that way, especially for the original contributors (though, it should be noted, the original author of KHTML, who wasn't really active at the time of the transition, did eventually fall into the WebKit camp).
Final note: this is just my somewhat fractured recollection of things from being in KDE community. My contributions to KHTML / WebKit were very minor (the original spellchecking support) so this may not jive completely with the folks that were closer.
Well, that's certainly over the top. Safari is a commodity.
It's pretty important.
If Safari magically disappeared today Mozilla would notice a bump in downloads and everyone would go with their day.
iOS on the other hand is a prison so I suppose those users would just be screwed.
WebKit, the rendering engine originally used in Safari (not Safari the application), nowadays powers Chrome, iOS, Android, BB and a hundred other browsers/platforms. In simple words: the absolute majority of mobile browsers use webkit, plus >50% of desktops/laptops.