From: Don Melton @apple.com Subject: Greetings from the Safari team at Apple Computer Date: Tue, 7 Jan 2003 11:31:10 -0800
Hi,
I'm the engineering manager of Safari, Apple Computer's new web browser built upon KHTML and KJS. I'm sending you this email to thank you for making such a great open source project and introduce myself and my development team. I also wish to explain why and how we've used your excellent technology. It's important that you know we're committed to open source and contributing our changes, now and in the future, back to you, the original developers. Hopefully this will begin a dialogue among ourselves for the benefit of both of our projects.
I've "cc"-ed my team on this email so you know their names and contact information. Perhaps you already recognize some of those names. Back in '98 I was one of the people who took Mozilla open source. David Hyatt is not only the originator of the Chimera web browser project but also the inventor of XBL. Darin Adler is the former lead of the Nautilus file manager. Darin, Maciej Stachowiak, John Sullivan, Ken Kocienda, and I are all Eazel veterans.
The number one goal for developing Safari was to create the fastest web browser on Mac OS X. When we were evaluating technologies over a year ago, KHTML and KJS stood out. Not only were they the basis of an excellent modern and standards compliant web browser, they were also less than 140,000 lines of code. The size of your code and ease of development within that code made it a better choice for us than other open source projects. Your clean design was also a plus. And the small size of your code is a significant reason for our winning startup performance as you can see reflected in the data at http://www.apple.com/safari/.
How did we do it? As you know, KJS is very portable and independent. The Sherlock team is already using it on Mac OS X in the framework my team prepared called JavaScriptCore. But because KHTML requires other components from KDE and Qt, we wrote our own adapter library called KWQ (and pronounced "quack") that replaces these other components. KHTML and KWQ have been encapsulated in a framework called WebCore. We've also made significant enhancements, bug fixes, and performance improvements to KHTML and KJS.
Both WebCore and JavaScriptCore, which account for a little over half the code in Safari, are being released as open source today. They should be available at http://developer.apple.com/darwin/projects/webcore / very soon. Also, we'll be sending you another email soon which details our changes and additions to KHTML and KJS. I hope the detailed list in that email will help you understand what we've done a little better. We'd also like to send this information to the appropriate KDE mailing list. Please advise us on which one to use.
We look forward to your comments. We'd also like to speak to you and we'd be happy to set up a conference call at our expense for this purpose.
Thank you again for making KHTML and KJS.
Please forward this email to any contributor whom I may have missed.
-- Don Melton Safari Engineering Manager Apple Computer
From: Dirk Mueller @kde.org Subject: Re: Greetings from the Safari team at Apple Computer To: Don Melton @apple.com [......] Date: Tue, 7 Jan 2003 21:18:19 +0100
On Die, 07 Jan 2003, Don Melton wrote:
> I'm the engineering manager of Safari, Apple Computer's new web browser > built upon KHTML and KJS. I'm sending you this email to thank you for > making such a great open source project and introduce myself and my > development team. I also wish to explain why and how we've used your > excellent technology. It's important that you know we're committed to > open source and contributing our changes, now and in the future, back > to you, the original developers. Hopefully this will begin a dialogue > among ourselves for the benefit of both of our projects.
I hope so too. I'm deeply impressed by your detailed changelog and by the changes. A few of the changes have already happened in "our" developing version and many of them were on our TODOs. For example just about this weekend I was working on improving the kjs garbage collector and now I read that you apparently already fixed the issues I had with it. Seems to me like a huge christmas gift. Thank you. Thanks a lot.
Especially I'd like to hope that we could set up a mailing list where we could exchange ideas, patches and bug reports. Also a common testsuite for regressions would be nice and probably help us a lot in developing KHTML and KJS further. Ideally the plan should be, and I hope you agree, to use a common codebase for the backend.
> Please forward this email to any contributor whom I may have missed.
Why KHTML (from the KDE mailing list) (Score:5, Informative)