2 ms·
I recall someone from Apple (I want to say David Hyatt) actually explained why they went the way they did. They looked at assimilating Gecko, but it was just to
by chc 15y ago
I recall someone from Apple (I want to say David Hyatt) actually explained why they went the way they did. They looked at assimilating Gecko, but it was just too large to mold into the product they wanted without essentially throwing out most of the existing product. But still, starting from scratch would have ballooned the budget since a Web browser is a nontrivial undertaking†. KHTML was a happy medium — it was a solid, functional base, but it wasn't yet overwhelming for the Safari team.
† 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).
- azakai 15y agoIt does make sense that KHTML was a compromise for Apple as you say. It's interesting that that was the motivation there, thanks for sharing that! 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).
- chc 15y agoYou're right, that isn't fair to Opera. I honestly just forgot about them when I was writing the postscript. Thanks for the reminder.