hebig.org/blog

2003January08
Current in Photos « Previous EntryHomeNext Entry »

Apple Safari: why they went for KHTML, not Gecko

Don Melton, Safari Engineering Manager: "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."

Translated through a de-weaselizer, this says:

"Even though some of us used to work on Mozilla, we have to admit that the Mozilla code is a gigantic, bloated mess, not to mention slow, and with an internal API so flamboyantly baroque that frankly we can't even comprehend where to begin. Also did we mention big and slow and incomprehensible?"

Seen at Blogzilla

Entry first published 2009-05-18 00:59, last edited 2009-05-18 00:59
Share this entry via e-mail - on Twitter