Well, Paul
Festa couldn't resist writing an article about the fact that
Apple decided to use KHTML instead of Mozilla. I love how he took
a bunch of stuff from Mike's diary
out of context and made it like Mike was only badmouthing the
browser, when he obviously wasn't. You have to read the whole
entry and it probably helps to know mike a bit to understand his
tone there. There's a lot of missed context with the way that the
article is written. Anyway, let's get down to business.
First of all, I don't think that we should be having the Safari
vs. Mozilla/Chimera discussion at all. It takes our eyes off of
the real prize and that
which we all should be worried about. I mean, if you control the
browser, you control the Internet. It sounds kooky, but it's
true. When we squabble amongst ourselves it doesn't do us any
good.
That being said, I do have a few things to say about the fact that
Apple is going this alone. First, it's great that they
decided to choose an open source solution, even if it isn't
Mozilla. If they manage to engage the KHTML community and get
well integrated with them then they have the chance to enjoy the
fruits of that relationship, like as we have with the Mozilla
project. The feedback loop of open source development will allow
them to both enjoy the fruits of the labor of the community and
the community benefits from the work that Apple does. Apparently,
as I understand it, they haven't been able to do this yet and have
been somewhat secretive about their involvement up until now.
We'll see if this changes but if it does it's good news for both
KHTML and Apple.
Second, another standards compliant web browser out there using
the web is only good news for everyone, assuming that they do it
well. Another browser means choice and choice means that everyone
wins since there's not one company in control of everything and
that means a more free Internet. From my understanding, KHTML
still has a long way to go to catch up with rendering real web
pages when compared with Mozilla but hopefully Apple will have
those straightened out by the time they do a final release so they
don't make life really rough for web developers.
Last I wanted to respond to some of the criticisms that are levied
at Mozilla in that article and in people's blogs as of late. When
I hear quotes like:
"When we were evaluating technologies over a year ago, KHTML
and KJS stood out," Safari Engineering Manager Don Melton
wrote. (KJS is KDE's JavaScript interpreter.) "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."
it really gives me pause. They are talking about Mozilla from
over a year ago. They are talking about a pre-1.0 Mozilla
release. Mozilla has gotten a lot better since that
evaluation, especially in the form of the Chimera project for OSX,
which has grown in leaps and bounds over the last few months.
It's like comparing a modern sedan with your 1976 Ford Pinto. Of
course, it's going to look better and drive better, it's newer.
We're not your mother's Pinto anymore.
Now, is our layout engine huge and ungainly and hard to
understand? Yes. Yes it is. And, at least to some degree it's
important to understand that Mozilla's layout engine has warts
because the web has warts. It's an imperfect place and that leads
to imperfect code. Remember that while KHTML is a good bit
smaller than our layout engine, it also doesn't render a lot of
sites anywhere near as well as Mozilla does. Over time, they are
going to have to add many of the same warts to KHTML as we have to
our layout engine. They might be able to do so in a more clean
way, but they will still be there.
Second, Mozilla's layout engine does so much more than what KHTML
is trying to do. We're rendering our entire application with it
so of course it's going to be bigger. Can we do better with our
layout engine in the future? Yep. Will we? Yes, I think that we
will. There's lots of interest in cleaning up the mess of layout.
In any case, I welcome Apple's entry into the web browser field,
even if it isn't using the software that I think is best suited
for the job. They can only make the web a better place. Unless
they screw up, of course.