WebKit project hit its monumental 100,000-th check in.
ariya.ofilabs.com
ariya.ofilabs.com
It's not like Webkit is simply a rebranded KHTML.
Especially since the reason for Webkit being open source could be that KHTML is LGPL. I doubt i'd be open source if KHTML were BSD/MIT style licensed. But that's just my opinion.
The only mentions I see on the page for "apple" are in raw statistics that explicitly mention that they are about fairly recent time frames. The first one has more commits from chromium.org than from apple.com
I also briefly browsed other pageson that site, but did not find any evidence for your claim.
Do you really expect every mention of "WebKit" to have a footnote explaining that it was based on KHTML?
I do no see a reasonable way to weave that remark into this post, I do not see any claim that this is even remotely an attempt to write the full history of WebKit, and I notice that, for those who do not know what WebKit is, the first occurrence of the term in the blog post links to WebKit.org, which says:
"WebKit is an open source web browser engine. WebKit is also the name of the Mac OS X system framework version of the engine that's used by Safari, Dashboard, Mail, and many other OS X applications. WebKit's HTML and JavaScript code began as a branch of the KHTML and KJS libraries from KDE."
I think that should be sufficient acknowledgement for anybody releasing code under the LGPL license.
But this discussion already is far more work and thought then my little remark in the beginning deserved...
For that matter, we don't know if things wouldn't have turned out better for Apple if it had started from scratch. For one thing, doing so would have avoided KHTML's LGPL license, which requires source code to be shared. That would have allowed Apple to make its web engine closed source or entirely BSD, which could have led to very different results than how things unfolded. Better or worse, it is very hard to say.
Edit: I'm curious, why the downmod?
We can obviously go round-and-round all day on which is the better engine. I'm only saying that Webkit was a successful project for Apple. I'm not sure how productive it is to second-guess it.
(I didn't downvote you).
I do think though that the KHTML/Gecko thing is a pointless debate. For one thing, both are very good, so I'm not sure what there is to argue. But the real issue is KHTML/Gecko is a false dichotomy: Apple has huge resources and amazing engineering talent, so it could have written a new browser engine from scratch, and I'm pretty sure that browser engine would have been awesome. And, doing so would have given Apple complete freedom to pick the project's license, either more closed than KHTML's LGPL license (even entirely closed source, like most of OS X), or more permissive (even BSD, like Apple prefers in its open source projects). There are a lot of interesting possibilities there, that we can only speculate about.
So again, I agree second guessing is pointless. But it just seems like debating KHTML/Gecko is even more pointless, given the other options Apple had.
† Think about it. HTML rendering engines are probably the most-used piece of software around these days, and yet in the almost 20 years since the Web came about, there have only been about 10 notable rendering engines written for it, of which only three have had real commercial viability (Gecko, Trident and WebKit).
About Opera, a comment: Opera definitely has real commercial viability. Unlike the other three you mention, Opera has had to be profitable all its life, and from the Opera browser itself (not subsidized by other products). Today Opera makes a lot of money from its mobile browser (but it is in danger from WebKit now).
I know the guy who has written that blog post, he was one of my colleagues when I was working at Nokia/Trolltech. This is where Lars Knoll (creator of KHTML) is still working at.
Real Artists Ship. By way of his kernel, Linus shipped GNU to a mass audience. And by way of WebKit, Apple shipped KHTML to a mass audience.
The parent thread read "Linux was a kernel that the GNU project added well after both projects were underway".
I was highlighting the fact that GNU is not responsible for the GNU/Linux combination in the sense that most distributions are not endorsded by the GNU project. Debian still has a GNU/Hurd version which got a little more official just a couple of months ago. They also have a GNU/kFreeBSD version.